Ask HN: What is a good product development stack for rapid launch to users?
10 comments
For a hobby project, solo developer to start means it is a personal choice. If you pick a stack that is new to you, carve out time to learn.
Don't bother considering popularity. If you are familiar with PHP and Python, see what frameworks for those are the best choice. For Python or PHP I have heard Django and Laravel are good frameworks, no experience with them personally. Model-View-Controller is a de-facto pattern with web frameworks and usually the framework will dictate file locations, structure of code, etc.
You mention data aggregator and users connecting data sources - that sounds like where the most technical work could be in your app. If this is consuming API's then that is pretty straightforward but if you get into screen-scraping or handling multiple ways to aggregate content then the available libraries/tools in your language of choice might influence your decision. I'd look into how you want to aggregate data first, see what tools are out there to help you.
Most web frameworks will out-of-box meet nearly all of your requirements. I'd be wary of code generation from a design tool. I'm not in the "must hand code everything" camp - it will work for an initial app but after you start adding features and changing things in your code the design tool that generates code won't match.
If you're up for learning something new, I would advocate for Rails. Once installed (along with DB) it has generators which can "scaffold" the parts of the app. I would guess PHP/Python frameworks have similar things. Google around for tutorials on this and try them out.
Don't bother considering popularity. If you are familiar with PHP and Python, see what frameworks for those are the best choice. For Python or PHP I have heard Django and Laravel are good frameworks, no experience with them personally. Model-View-Controller is a de-facto pattern with web frameworks and usually the framework will dictate file locations, structure of code, etc.
You mention data aggregator and users connecting data sources - that sounds like where the most technical work could be in your app. If this is consuming API's then that is pretty straightforward but if you get into screen-scraping or handling multiple ways to aggregate content then the available libraries/tools in your language of choice might influence your decision. I'd look into how you want to aggregate data first, see what tools are out there to help you.
Most web frameworks will out-of-box meet nearly all of your requirements. I'd be wary of code generation from a design tool. I'm not in the "must hand code everything" camp - it will work for an initial app but after you start adding features and changing things in your code the design tool that generates code won't match.
If you're up for learning something new, I would advocate for Rails. Once installed (along with DB) it has generators which can "scaffold" the parts of the app. I would guess PHP/Python frameworks have similar things. Google around for tutorials on this and try them out.
Django without a doubt. It will handle ORM, frontend, backend, etc. It does the entire stack end to end and has built in migrations too, unlike Node. Please don't fall into the JS trap, it sucks. You can easily use django rest framework to redo the frontend with something like React later on without massive backend changes.
Never done anything close, just curious, I still need JS for frontend right?
Technically no. Django uses templates which can be pure HTML if you want. You can add JS if you want to, but its not required. In fact server side rendering is one of the most common ways to serve sites that don't need to be dynamic in the browser
I used Rails + PostgreSQL + TailwindCSS / TailwindUI (design system) + AlpineJS (for reactivity, screw React). Deploy to Heroku for minimum hassle, but if you know some Ansible stuff, deploying it to VM is quite straightforward too.
Build and launched a web app in 5 weeks (using time after work and weekends), bonus is that I get my first paying customer three weeks after launch! And I have been iterating my app feature based on customers suggestion ever since
Build and launched a web app in 5 weeks (using time after work and weekends), bonus is that I get my first paying customer three weeks after launch! And I have been iterating my app feature based on customers suggestion ever since
If you’re wanting something super simple check out UserBase https://userbase.com . You haven’t given a lot of requirements here so there’s not much to go on.
Variety and volume of the 'data' concerns me. Are we talking 100 rows or a billion rows?
Does the system store the data the user is working on permanently or just the metadata?
Does the system store the data the user is working on permanently or just the metadata?
We are talking roughly 10s of rows of data per user per day stretching back at most a few years. So no huge volumes. Mostly read.
I would like data to be persisted across user sessions. And refreshed either periodically, on user login, or on user action. Depending on source.
I would like data to be persisted across user sessions. And refreshed either periodically, on user login, or on user action. Depending on source.
The boring database favored by engineering managers is Postgresql.
React + MobX provides, I think, a good answer to the problem of "how do i update the user interface to reflect changes to the application state?" on the front end.
Commercially I have seen Java used almost exclusively for web back ends, really because it handles the kind of concurrency that matter for servers well. .NET is about the same but less popular.
It is easy to write small servers in Python and you can do really fun things with async/await (e.g. bridge message queues) but because Python is fundamentally single threaded the concurrency story is worse than Java. With node.JS you could write both your front-end and back-end in the same language, which sounds appealing, but hardly anybody does it.
React + MobX provides, I think, a good answer to the problem of "how do i update the user interface to reflect changes to the application state?" on the front end.
Commercially I have seen Java used almost exclusively for web back ends, really because it handles the kind of concurrency that matter for servers well. .NET is about the same but less popular.
It is easy to write small servers in Python and you can do really fun things with async/await (e.g. bridge message queues) but because Python is fundamentally single threaded the concurrency story is worse than Java. With node.JS you could write both your front-end and back-end in the same language, which sounds appealing, but hardly anybody does it.
Any of the batteries included frameworks should be just fine to get started. You know Python and PHP, so I'd check out Django and Laravel.
I am looking to start a hobby project to build an application. And I want to get to something that is working for users with as little work as possible. The app is mainly a data aggregator that helps users collect and consolidate data from multiple different sources. Users would create an account and connect data sources. Then they can view aggregated data from multiple data sources.
I am looking for a stack that gets me as far as possible with minimal work. I want to spend as little time as possible on anything but business logic and presenting data in a nice UI. I can accept something quite opinionated if that helps. I would like a web app that handles user login and keeps some data for users. As well as integrating with 3rd party providers for data.
I would like to cover:
- Design system (that I can use in Figma) which translates into what the application will look like, and is easy to implement
- Boilerplate and project setup/structure (I want to spend time on features, not structuring code) - Development of the UI (UI framework to work with the design system)
- Backend development (for the web app)
- Data persistance (i.e. a DB)
- User login (can I avoid reinventing the wheel to let users create accounts and login?)
- Development environment (I want to rapidly see and test what I create)
- Hosting (fine to run locally at first)
Additional nice-to-haves:
- Cross-platform development to allow me to add native apps for iOS and Android
I have not written code in a while. I have past experience in single-page JS applications (using frameworks that no longer seem to be popular). I have experience using node, Python and PHP for backend development. Could take the opportunity to learn something new if the benefits are big enough.
Please share your suggestions on full stacks. As well as your experiences and learnings.
Edit formatting.