Follow our Telegram channel to get notified instantly whenever new books are published.
I Have An App Idea – Amanda Spann

Now, this is the part where doing your homework pays off. If you took the time to complete chapter 7’s wireframe cataloging activity, you already have a major head start on listing the requirements, features, and functionality you want to include in your app. The natural next step here is to consolidate each of the elements, key features, and integrations you listed below each of your wireframes into one comprehensive requirements document. But before we do, I’d like to remind you that we’re still striving to create an MVP of your app—the leanest, most simple version of your product to test with your audience.
The more requirements and features you have, the more costly this will be to build. Prioritizing features can be a tough task because each requirement may feel like it plays a key part in your vision. However, feelings aren’t necessarily facts. Ask yourself: Do you really want to spend thousands more on an array of features that aren’t essential to proving your concept or running your business and that you aren’t 100 percent sure your customers will love?
It’s a big risk to take! “When it comes to building a start-up, perfect product specifications don’t exist; things change too rapidly. Help the dev team understand the why and where you are hoping to get to. Then guide them to fill in on the how.”2 ~Dan Kihanya, Director REI Path Ahead Ventures, Creator of Founders Unfound Podcast To make the selection process a little easier I’d like to introduce you to the MoSCoW method,3 a prioritization technique that helps you trim the fat by categorizing every one of your app’s requirements into four categories.
Your must-haves are your nonnegotiables; you need them to run the app, to be compliant, and for the app to be legal or make money. Then you have your should-haves; these are requirements that would be amazing features, but they’re simply not vital. The difference between them and the next category is that they tend to be points of distinction and differentiators, but at the end of the day, they’re still not essential to the bottom line of your app.
Could-haves are nice complements, but they’re just garnishes to your musts and should-haves. If you find you have extra money in the budget, these could be good add-ons.
This book is dedicated to all the dreamers who became doers, the self-starters, and those who are committed to making it happen. I see you. You are worthy. Your ideas have power. I can’t wait to see them take form. Thank you to my family—Dad, Mom, Dee, and Mira. Being a part of our unit is a blessing.
I could not have asked for a greater gift. And last but not least to my community of friends, colleagues, and counterparts who supported, contributed, and offered guidance in the production of this project. Thank you for believing in my vision. I am eternally grateful. OceanofPDF.com Introduction Prepare to Build I’m a publicist by trade. I didn’t go to school to be a developer.
I’m honestly not sure I’ve ever written a full line of code in my life. Well, outside of Myspace. Shout-out to Tom! Yet, I’ve created and turned a profit from apps that have been downloaded by thousands of people around the world, and I believe that you can too. It’s important for me to be transparent about who I am and why I’m doing this. I’m not here to sell you on some shoddy guarantee that you’ll become an app store millionaire overnight or to give you some sleazy magic bean upsell.
I am at my core an entrepreneur who happens to be passionate about helping people actualize their ideas. I graduated from college at the height of the Great Recession and didn’t have the money or the resources to build the brick-and-mortar business of my dreams. So I turned to apps because I believed that even if I didn’t know a thing about building them, they were the quickest and most affordable and accessible means for me to become an entrepreneur.
I still believe this now. I wrote this book because I get a constant stream of emails and letters from people who have app ideas but have no clue where to start, or who have taken the leap to start building an app themselves but are running into some costly challenges that could have likely been avoided if they would have had some insight into what to expect before they got started.
I Have an App Idea is my “reply all.”
This is a short excerpt from the opening of “” by Unknown, quoted for review and introduction purposes. All rights belong to the copyright holders.
Book Information
- Unique ID: 9eec688e7a03796b
- File Extension: .pdf
- File Size: 8,425,273 bytes (8.035 MB)
- Title: –
- Author: Unknown
- Pages: 269
- Language: English (en)
Reading & Word Statistics
- Estimated Reading Time: 239.88 minutes
- Total Words: 47,975
- Total Characters: 288,048
- Average Words per Page: 178.35
- Average Characters per Page: 1070.81
Most Frequent Words
app (925), apps (194), users (167), development (139), store (138), product (137), like (124), time (122), need (120), make (107), use (103), you’ll (99), team (97), user (97), features (96), you’re (93), process (90), build (89), one (88), developer (87), work (86), get (83), business (83), it’s (78), developers (77), information (77), content (76), people (75), find (75), take (74), new (73), many (71), want (71), design (71), com (69), google (69), provide (68), also (67), even (64), testing (63), project (62), start (62), play (62), don’t (61), building (60), review (60), apple (60), often (56), requirements (56), now (55), best (54), app’s (53), problem (53), see (52), following (52), first (52), test (52), data (52), available (50), know (50), chapter (50), much (50), idea (48), way (48), access (48), market (48), feel (48), likely (47), right (47), help (46), key (46), used (46), code (45), feedback (45), next (45), page (45), experience (44), yourself (43), step (43), search (43), create (43), include (43), web (43), well (42), https (41), mobile (41), things (40), model (40), ensure (40), services (40), give (39), set (39), software (39), platforms (39), stores (38), money (37), using (37), name (37), without (37), select (37).
