Do you document your app idea before jumping into code...
Gyen Abubakar Sadick
4 replies
...or you jump straight into code, like me 🥲? Whatever your approach is, what are your thoughts about it?
Replies
Amanda Trincher@amandatrincher
Yes, all the time, it's like planning a project, and it helps you not miss out on details, or anticipate some complexities while coding. Agencies like https://coaxsoft.com/solutions-m... are now using similar methods to get the job done better
Share
NVSTly: Social Investing
we note everything down, don't get into it until we have a full understanding of how each feature will work. saves a lot of time from getting into it without knowing exactly and running into an issue or it not possible the way its wanting to be intended, etc.
It personally took me over 2 years to document everything. I started with Balsamiq Wireframe as I am not a dev myself. My goal was to make the design of the interface, and more importantly, the technical aspect of the app.
My SaaS is built for the agriculture industry. If you can't provide an extended amount of data to simplify the process, the dev will not get it.
Now I am working with two devs, and as @krishna kumar said, get all your documentation in order, every detail is crucial when you want to integrate some complex features.
Hope it helps!
Document it extensively with workflow drawings and coarse screen diagrams by the ton. Helps ensure that small small ideas are not lost. Also, helps refine the idea. But maybe that is because I am not a dev myself.