Devbook

Search engine for developers

1.0
β€’1 reviewβ€’

11 followers

Devbook is a search engine for developers that helps them to find the resources they need and answer their questions faster. Fast, accessible right from a code editor, and fully controllable with just a keyboard.
Devbook gallery image
Devbook gallery image
Devbook gallery image
Devbook gallery image
Devbook gallery image
Free
Launch tags:Productivityβ€’Developer Tools
Launch Team
Auth0
Auth0
Start building with Auth0 for AI Agents, now generally available.
Promoted

What do you think? …

Vasek Mlejnsky πŸš€
Hey PH community! πŸ‘‹ @valentatomas and I started building Devbook when we realized how much time we spend on googling and going through different websites when coding. Current general internet search engines weren't made for developers but they're a tool that every developer is using almost every day. We felt like we are sometimes losing hours per week searching on the internet. That's why decided to build a search engine for developers. Starting with Stack Overflow and official documentation. We are both developers and have been working together for more than 11 years. With Devbook, our productivity has increased. It's now also easier to stay in the coding flow because we don't have to leave our IDEs and go to the browser so much. We just hit a shortcut to show Devbook, get what we need and go back to coding. 10x faster than going to a browser. This is how Devbook works πŸ‘‡ Devbook is a desktop app that works similarly to Spotlight on macOS. You hit a global shortcut and can start searching in Stack Overflow and docs right away. Since Devbook appears as an overlay on top of an app you're using right now, you don't have to leave your editor at all. Devbook can be fully controlled with just a keyboard. Even copying code snippets can be without touching a mouse. πŸ“š Currently we support these docs * Python * Pandas * Scikit * PyTorch * Jest * Mocha * Chai * Golang * Elixir * Flask * Django * TypeScript * Rust * React * Rails * Ruby * Web DOM API * Nunjucks * NPM * Node.js * HTTP * HTML * Docker * NumPy * CSS * JavaScript
 We are continuously adding more. We are also working on a way to add docs for NPM packages, PIP packages, Rust crates, etc. A lot of exciting features are coming to Devbook this year. πŸ’° Pricing: Free. We want Devbook to be free for solo devs. Later on, we will introduce premium plans for teams. We would love to learn what you think so we could make Devbook better. With your feedback we can make developers better and more productive! πŸ™ - Vasek (co-founder)
Tyler Swartz
@valentatomas @mlejva this looks super cool. What sort of benefits/features are you thinking will go into the premium team plans?
Vasek Mlejnsky πŸš€
@valentatomas @tylerswartz Hey Tyler, thank you! We have a lot of different feature requests for teams but the most requested ones so far are: 1) Anonymous analytics to see what are folks in the team searching for (requested by team leaders) 2) Search in organization repos 3) Search in organization docs/knowledge 4) Bookmark results and make them accessible for the whole team 5) Search in specific Slack channels like #Engineering Anything you might find useful in a team version of Devbook? By the way, Reddit has been one of the most helpful ways to reach out to developers and introduce them to Devbook. For example, our post to /r/python has been extremely helpful in gaining momentum - https://www.reddit.com/r/Python/... What a nice community :)
Ivanna Wendel
Great useful product! Well done!
Vasek Mlejnsky πŸš€
@ivanna_wendel Thanks! More cool stuff to come soon!
Ivanna Wendel
@mlejva That's really cool!
Michele Piccirillo
Great idea! One quick suggestion, from being a long-time fan and user of https://devdocs.io/: it would be nice to be able to select more than one active documentation source and keep them active persistently – for example, if my stack is TypeScript on Node.js with Jest, I would probably like to search across TypeScript, JavaScript, Node.js and Jest all the time without switching sources. For the rest, brilliant product! Love how you kept everything navigable through keyboard πŸ€“βŒ¨οΈ
Vasek Mlejnsky πŸš€
@lordofthelake Thank you, Michele. Being able to search in multiple resources (like multiple docs) is exactly what we are working on right now. We are rebuilding our search engine to support this!
Michele Piccirillo
@mlejva Nice! πŸŽ‰Can I be the picky customer once again and ask if you have any plans to implement search-as-you-type as well as part of that? πŸ˜… That would be πŸ”₯
Vasek Mlejnsky πŸš€
@lordofthelake Michele, we love picky customers :). We had that feature but weren't happy with the overall experience. We will consider implementing it in a better way and giving it a comeback πŸ˜ƒ
Simon
Great product, it really helps me working more productive
Vasek Mlejnsky πŸš€
Thank you, @simon_csaba!
Sanket Makhija
Within seconds of the product introduction, I'm sold on the idea of this product. Kudos for an amazing product.
Vasek Mlejnsky πŸš€
@sanket_makhija That is awesome! πŸ™Œ Any feedback you might already have on your mind?
Sanket Makhija
@mlejva Add Cheat Sheets like, http://devhints.io/. Make it more awesome
Henrique Doro
Brilliant idea, Vasek & TomΓ‘Ε‘, thanks for building it! I'm trying to use it in my Windows laptop, but I can't go past the initial screen as the button is hidden at the bottom and I can't scroll - my screen size is quite small and zoomed-in. May be worth some debugging πŸ™ˆ
Vasek Mlejnsky πŸš€
@hdoro Oh shoot! We didn't test this use-case. I just deployed a quick hot-fix that should solve this for now: 1) Reload Devbook (Ctrl+R or completely close the process and start it again) 2) You still won't see the next button but you are now able to press enter to go to the next page during onboarding. Just a note, on the last page you have to hit the global shortcut to be able to finish onboarding. Please let me know if it helped and I'm super sorry for the bad experience. We are going to fix this!
Henrique Doro
@mlejva No need for apologies! Bugs happen even in the simplest of sites, right? Thanks for the quick reply and best of luck with the rest of your launch πŸ™Œ
Jessie Foley
Since it's a search engine for documentation do you plan on allowing users a way to add their own internal or custom documentation for like homelab environments or user-specific usecases somehow? Example. I'm learning docker-compose currently and i'm setting stuff up on a laptop in my house, could i somehow add documentation -- to list out what computer it's on the static ip of the computer, necessary passwords and any other documentation of my setup, -- and be able to search that within devbook when i'm working on my compose files on my local machine, or even potentially host devbook custom files and sync them between my computers for access anywhere?
Vasek Mlejnsky πŸš€
@jester5537 Hey Jessie, yes we plan to offer a support for plugins. Plugins will make Devbook programmable. This way you will be able to upload own docs, let Devbook index them and later search in them. We've been also thinking about offering self hosted solution for teams but that isn't clear right now. Support for plugins is a little bit down the roadmap.
123
β€’β€’β€’
Next
Last