About the quiz, the recommendations, and the site.
No. The quiz runs entirely in your browser. Your in-progress
answers are saved to your browser's localStorage so
a refresh doesn't lose your place, but nothing is ever
transmitted to a server. Details in the
privacy policy.
No - it's a sensible default based on a handful of answers, not a verdict. See how recommendations are made for the reasoning and its honest limits.
Yes. Starting with a recommended stack doesn't lock you in - core programming concepts (state, functions, requests, queries) transfer between frameworks and languages more than it feels like when you're just starting out.
A single different answer - especially about hosting or experience level - can change the result, since the logic branches on those early. The comparison pages show the full set of trade-offs behind each category, not just the one path your answers took.
Not for Firestore specifically - it's a NoSQL, document-based database, so you won't write SQL queries against it. That said, SQL is worth learning regardless, since it's the query language behind PostgreSQL, MySQL, and SQLite, and shows up constantly in job listings even for developers who mostly use NoSQL day to day. See the database comparison for how Firebase stacks up against SQL options.
Often no. For a portfolio or basic content site, plain HTML, CSS, and JavaScript loads faster, has fewer moving parts, and teaches you the fundamentals every framework builds on. Reach for a framework once your interface has real interactivity or shared state to manage.
Match it to the closest category: "shared hosting" means a plan where PHP/MySQL are pre-installed and you upload files (most budget hosting, including Hostinger); "VPS or cloud" means you have full server control (DigitalOcean, a Linux server you manage yourself); "platform service" means a provider that runs your app for you from a Git push (Railway, Render, Heroku-style). See the glossary entry on hosting for more.
The primers are a fast orientation - what a technology is, when to use it, and your literal first steps - not a full course. Each one links to official documentation under "go deeper," and most also point to a follow-up primer for the natural next skill to learn. Treat them as the map, not the whole trip.
No. Every technology in the quiz and primers is free to start with - either fully open-source or offering a free tier generous enough for learning and small projects. Recommendations aren't influenced by affiliate deals; there aren't any.
Yes. Every result includes a "What would change this pick?" section listing each single answer that, if different, would lead to a different recommendation - so you can see which of your constraints actually decided it. Each result also links to a full write-up, and all 16 possible results are listed in one place.
Yes - use the "Copy link" button on the result screen. Your
answers are stored after the # in the link, a part
of a web address that browsers never send to the server, so
sharing a result still doesn't transmit your answers to Stack
Picker. Anyone who opens the link sees the same result.
Stack Picker is written and maintained by Stuart Mathieson, an independent web developer based in Scotland. It's an independent project with no sponsors or affiliate deals - see the about page for the editorial policy.
Yes - email [email protected]. Spotted an outdated detail in a primer instead? Same address; the contact page lists what helps.