Start by considering the simple question, “what pain does this alleviate?” and then writing down the answer. That’s the goal of the application. Next, you need to explicitly define what your application does to solve the problem — not in terms of features that can be put into bulletpoints but as an overarching solution. This is your killer idea. Finally, you should lay out what your application does at a feature level to support that idea.
- 2011-2020 Agile Apple ASP.NET Cloud Companies Comparison Creativity Databases Deliberate Practice Experience Google Innovation Learning Management Microsoft Mobiles Predictions Productivity Programmers Programming Project Management SDLC Skills SoftwareCraftsmanship SQL-Server Success Super Uncategorized VB.NET
Top Posts & Pages
- RT @SingleFounder: Thanks to all of those who attended #MicroConf this year. Hope to see you again next year! 3 days ago
- Do I Have What it Takes to be a Senior Engineer? | Codementor bit.ly/2rqmJYZ 5 days ago
- Why Windows must die. For the third time zd.net/2qWVaFF via @ZDNet & @jperlow 1 week ago
- “The truth is in the code” by @BertilMuth medium.freecodecamp.com/the-truth-is-i… 2 weeks ago
- Learn Through Delivering flowchainsensei.wordpress.com/2017/04/24/lea… via @flowchainsensei 4 weeks ago