What's the best way to approach building a product? Specifically an App or WebApp?
I tend to just get an idea, and try to use AI now to get a basic framework. Then after kinda aim to get the core functionality down before moving towards UI and Design...however I often get stuck once it's on UI design as I can never get it the way I like.
As I try to add more features I kinda get lost in the code and then break other things and eventually either abandon the app or simply decide to keep it super simple at the expense of features.
Does anyone have any recs or process that could help in my app making journey? TIA!!
@kenny_hawkins That's a good take on distinguishing between nice-to-have and must-have features while building the MVP! 😊
I know the feeling tho. If you ship it fast. It wont be eligible to get featured on PH, its too rough. But stepping stones right. You can get 20-30% of the traffic a feature spot would get you by sharing it on Linkedin. If it has some spark, it should trend on Linkedin if you give it a little push. If that happens. Now you know it has potential. So you double down on refining it making it ready for the big stage. A PH featured spot 🤘
As a former SaaS founder, this was my approach to building a product:
Identify a Problem – I started by spotting a gap and validating it with people in my network who might be experiencing it.
Document Everything – I created a Google Doc outlining the problem, solution, ICPs, use cases, key features, and pseudo-code.
Design the UI Flow –
Sketched rough wireframes on my iPad.
Refined them using Excalidraw.
Finalized high-fidelity designs in Figma (now leveraging AI is possible).
Decide on Development Approach –
If possible, used no-code/low-code tools.
Otherwise, outsourced custom development to dev friends (or AI-assisted coding).
Build & Launch the MVP – Focused on core functionality, launched fast, and got early users.
Iterate & Scale – Based on user feedback and roadmap, I gradually added more complex features.
Since ideas tend to grow in complexity the longer they stay in my head, I prioritize execution and marketing as early as possible.
@gabe I saw your website and found Shh... interesting. Definitely a good one! Feature request in advance: if possible, create an option to mute the mic without showing on the meeting app we are muted LOL
I am cheering for you! :)
Before building anything, start with the problem.
Research and survey to see if your product solves a real problem or adds value to anyone's life. This will shape the roadmap of features for the product around the user instead of the creator.
Then once the idea is validated, identify the simplest version of the application that can be built, shared, and used to validate the concept in the market with users. Outline these features and prioritize the highest-value ones.
Then if possible, use the fastest method of development (AI, no code platforms, outsourcing) to get a working demo. If you are a developer like myself, it can be fun to write the code and learn, but ultimately you are trying to build a product so the faster you can get there the better, even with help.
Use simple frameworks, languages, and deployment strategies. For web apps specifically, more times than not, basic HTML/JS/CSS is plenty to get something going for the whole stack.
For apps, maybe try a hybrid app framework like Ionic (which I love), that allows you to build the product once and deploy in many places. This allows for fast prototyping.
It's easy to be distracted by the look and feel of things. I like what @rohanrecommends outlined. When taking notes, stick to the absolute minimum for the MVP. If you are thinking about a feature that would "be nice to offer/have", postpone it. Once you have the MVP, you have an idea of how your product will function and react. Add those other features you just HAVE TO HAVE before launch, and then dedicate the remainder of the prelaunch building to marketing, copy, and design. Can't wait to see what you make!