<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Troy Anderson on Medium]]></title>
        <description><![CDATA[Stories by Troy Anderson on Medium]]></description>
        <link>https://medium.com/@alliedcode?source=rss-7e378ac6d77f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*5Fc6Crq4_SIyEpOrZkYEGA@2x.jpeg</url>
            <title>Stories by Troy Anderson on Medium</title>
            <link>https://medium.com/@alliedcode?source=rss-7e378ac6d77f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 10:19:16 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@alliedcode/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How To Bring an App to Market, Part 5: What Does It Cost To Launch an App? • Allied Code]]></title>
            <link>https://medium.com/@alliedcode/how-to-bring-an-app-to-market-part-5-what-does-it-cost-to-launch-an-app-allied-code-f8ee0e7ea38?source=rss-7e378ac6d77f------2</link>
            <guid isPermaLink="false">https://medium.com/p/f8ee0e7ea38</guid>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[developer]]></category>
            <dc:creator><![CDATA[Troy Anderson]]></dc:creator>
            <pubDate>Tue, 06 Mar 2018 20:20:52 GMT</pubDate>
            <atom:updated>2018-03-22T21:01:04.993Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/833/1*o_rBoyy92yUtMduCwEyhkA.jpeg" /></figure><p>When I tell people I develop apps, this is the typical response: “Oh, I have an app idea.” They spend about a minute describing it, then ask, “What it will cost to create?”</p><p>It may not surprise you that the answer is longer than a typical cocktail party talk. There are many variables. But here’s an overview that I can cover in the time it takes to drink a six-ounce pour of cabernet sauvignon:</p><p><strong>Features and Complexity</strong></p><p>It’s probably fairly obvious that the number of features and their complexity drive the cost, so spend some time identifying only the features that are required to deliver your core offering. In other parts of this blog series, we discuss how this strategy will reduce your development cost.</p><p><strong>Platforms</strong></p><p>Different platforms — Apple iOS, Android, web — have different cost characteristics. In general, iOS app development costs less than the same app developed on Android. Web apps are often the least expensive.</p><p>Some apps are quite successful on a single platform. Others must be on all platforms to be useful. Building for multiple platforms at the same time is the most costly approach. During development, your developer is not just coding the features, but is also getting feedback from you and users on what works and what needs to change. Developing for one platform first lowers those iteration costs. When you are 80% complete on the first platform, begin the second.</p><p><strong>The Cloud</strong></p><p>The cloud is used for persistent and/or synchronized data storage, such as when you want the same data to be available on multiple devices or on a device plus a web app. To tie data to specific users, you must authenticate them via the cloud. Other cloud services such as push notifications and social media integration are also useful features. All of these cloud services add cost to the project.</p><p><strong>Developers</strong></p><p>The proliferation of low-hourly-rate overseas developers comes with a host of problems: differences in culture, language, time zones; communication breakdowns; dubious security. Many who try this route regret it. In fact, many venture capital firms will not invest in projects developed overseas.</p><p>Even in the United States, you don’t always get what you pay for. Some large firms assign a product manager who sees your product from inception to completion. But if the firm has competing priorities, your team might be switched out — especially if you’re a smaller business.</p><p>With smaller firms, you can get to know your team and assess their quality. If they meet your needs, you will likely be working with the same people throughout your development project. You will be a big priority for them. Often you can get better pricing in this category.</p><p>Finally, a solo, independent developer can be a great fit for a proof of concept. But beware, even moderate projects require five roles: Project Manager, Product Owner, Scrum Master, Developer, and Quality Assurance. It’s impossible for a single person to hold all of these roles. So for anything but the smallest projects, consider augmenting the solo developer with additional team members.</p><p><strong>Ok, But What Does It Cost?</strong></p><p>Even apps without any server component or API integration can be complex and challenging. It comes down to the app’s feature set. With any professional firm where you can trust the result, you’re starting at around $25,000.</p><p>Apps with a back end and more complex feature set — including social media integration, user on boarding flows, cloud data storage or synchronization, push notifications, etc. — app development starts at around $75,000 and go to $250,000 or more. Again, start small and work with your developer to identify the minimum feature set that will enable you to get feedback from real users. Use their feedback to prioritize your budget and timelines. Time and effort spent there will pay off in both cost and quality.</p><p>While there are simple games, many games include asset creation such as sound effects, a sound track, and 2D and/or 3D animations. Developing games can be like making a movie, with a movie’s production budget!</p><p><strong>Beyond the App</strong></p><p>The cost of bringing an app to market goes beyond user interface, design, development, and project management. Be sure to budget for ongoing updates and potential server costs. If you’re providing app support, remember to pay yourself.</p><p>Now that you have your app, you need to tell people about it. Everyone hopes their app will ‘go viral’ through social sharing, and therefore cost little to advertise. But the reality is, while you can make it easy for users to share your app or invite others, having them actually use those features is impossible to engineer. So don’t bank on it.</p><p>Instead, consider that for the less expensive range of app development cost ($25K — $50K), you may spend as much marketing the app as you did to develop it. There are millions of apps available. Imagine your app as a book on a library bookshelf: how much would you have to spend to get people to walk into the library and ask for that one book? That’s what searching the app stores is like. For mid-range and expensive apps, the marketing cost may be only 10–25% of development cost.</p><p><strong>The Big Picture</strong></p><p>Many people are drawn to creating apps because they see a consumer need and think of an app that meets that need. As businesses go, developing an app does not represent a large startup cost. But it’s also true that an average app will not pay its creator as much as a full-time job.</p><p>‘Hobbyist’ or occasional app creators do occasionally succeed in launching an app that augments their income. But as the old saying goes: “Hobby time invested equals hobby money.” The most successful apps fall into two categories: those that support an existing business, and those that <strong>are</strong> the business. The former are those that expand or increase the efficiency of an existing business, enabling it to engage with its customers in a new or more useful way. The latter are well funded, allowing for development iteration and significant marketing and operational costs.</p><p><em>Originally published at </em><a href="https://www.alliedcode.com/cost-to-develop-an-app/"><em>www.alliedcode.com</em></a><em> on March 6, 2018.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f8ee0e7ea38" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[“How To Bring an App to Market” Part 4: From App Idea to App Launch in 10 Steps • Allied Code]]></title>
            <link>https://medium.com/@alliedcode/how-to-bring-an-app-to-market-part-4-from-app-idea-to-app-launch-in-10-steps-allied-code-41b670a6c6b6?source=rss-7e378ac6d77f------2</link>
            <guid isPermaLink="false">https://medium.com/p/41b670a6c6b6</guid>
            <category><![CDATA[development]]></category>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[developer]]></category>
            <dc:creator><![CDATA[Troy Anderson]]></dc:creator>
            <pubDate>Sun, 04 Mar 2018 03:25:49 GMT</pubDate>
            <atom:updated>2018-03-20T17:01:01.427Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*bKGlSQUvVN2LF9m-hR1-EA.jpeg" /></figure><p>Previously in this series, we’ve covered how to originate app ideas, and why and how to ideate those concepts. But how do you turn your app idea into reality? Use our 10 steps countdown:</p><p><strong>Step 1: Write Down Your Features</strong></p><p>This exercise helps you focus on and expand your idea. Your app should have popular and unique features that are clear and easy to understand. The resulting list will help you discuss your app with co-founders, designers, investors or developers. (IMPORTANT: have people sign a non-disclosure agreement before discussing your more unique app features.)</p><p><strong>Step 2: Research Your Market</strong></p><p>Identify your competition and market needs and trends. Similar apps in the market are not necessarily bad news — they can be proof of your concept. But if they exist, learn their reviews, ratings, strengths and weaknesses. How will your app be different and better? If you make changes, update your feature list.</p><p><strong>Step 3: Identify Your Users</strong></p><p>Who will use your app, and who will be your marketing audience? Consider their demographics, psychographics, consumer behavior, careers, and industries. If needed, re-engineer your app and its features to fulfill their needs and desires. Gather small groups of your audience (8 or fewer) and ask what they like or dislike about your app concept and features. Write down what they say and reflect on it later instead of insisting that your original concept was best.</p><p><strong>Step 4: Monetize It</strong></p><p>Subscription fee? In-app purchases? In-app ads? Selling user data? Sponsorships? Fee Trials? Some of these approaches will work better than others for your app, audience and market. Select the one or two that offer the best profit potential.</p><p><strong>Step 5: Create a Rough Sketch or Wireframe</strong></p><p>A wireframe helps define your concept and refine the requirements of your product. You can draw a rough sketch with paper and pencil, use online tools to create a wireframe. This helps you chart your app’s navigation. This doesn’t require technical skills, but you should understand how navigation works. Your wireframe and features list form the specifications for the app to be built.</p><p><strong>Step 6: Select a Developer</strong></p><p>Up to this point, you may have accomplished this list comfortably. But unless you are a developer, this step is where you will need help. Acquiring that helps presents a problem: how do you sort through developers when you don’t have the technical knowledge to evaluate their work?</p><p>This is where the ‘CTO Service’ model makes sense. Allied Code offers this service. We review the work you’ve done, ask questions, make clarifications, then locate more than one developer who will deliver a quality app at competitive cost. We supervise the bidding process to ensure that all bids meet your specifications and are ‘apple-to-apple’ comparisons. Then we advise you on which vendor we think will work best for you, considering development methodology, workmanship, development cost, schedule, ease of communication, and accessibility.</p><p>Once you have selected a vendor, we can continue to supervise them and advise you, so — speaking bluntly — no one can take advantage of your inexperience in developing software.</p><p><strong>Step 7: Design the User Interface / User Experience</strong></p><p>This critical phase enables you to iterate on ideas while minimizing development costs. A good developer will provide significant and valuable insights here, and it is worth paying for that expertise to avoid common pitfalls. Have your developer create a detailed wireframe so you can visualize each screen of your app and its overall function and flow. You may decide to add or delete features. Next, have your developer create your app’s visual design: color, theme, typefaces, graphics. At this point, you’ll have a near-final picture of how your mobile app will appear and flow. Ask your developer to reconfirm the development plan, time and cost.</p><p><strong>Step 8: Develop and Test</strong></p><p>During development, ask your developer to demo or send you the app-in-progress each week for your testing and comment. (In another post, I’ll discuss the pros and cons of using an Agile development methodology. Generally, it’s a great idea when done well.) The purpose of the demo or getting a test build is to see the progress, have an opportunity to make corrections or changes early on, minimizing the cost (effort, time, and money) of change later. As the app gets more features, ask friends to test it as well. You may think of new features; if so, discuss them with your developer and ask the time and cost involved in adding them. If adding them exceeds your budget, you can add them later in an app update.</p><p><strong>Step 9: Launch and Market</strong></p><p>Once you are satisfied with your app, launch it in iTunes App Store and the Google Play store. Now it’s time to get the word out. You may want to hire a company like Allied Code to help you market your app. Whether you hire someone or DIY, a good place to start your marketing is social media. Facebook — which has more users than all other social media platforms combined — offers extremely detailed audience targeting. To gain earned media coverage, send a download link to tech bloggers and reporters and ask them to review your app.</p><p><strong>Step 10: Gather Response and Prep the Next Release</strong></p><p>Collect user data, market response, and app demand. Early on, learn why people download it and why others don’t. This provides you direction for changing your app and doing a new release. As your app succeeds, keep engaging with your users to plan the next release. With your data and learning, your app should continue to improve and grow. If it does not, talk to potential users about the problem you’re trying to solve or the engagement you’re trying to create, and listen to their concerns. Incorporate what you learn and release an improved version.</p><p><em>Originally published at </em><a href="https://www.alliedcode.com/from-app-idea-to-app-launch/"><em>www.alliedcode.com</em></a><em> on March 4, 2018.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=41b670a6c6b6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[“How To Bring an App to Market” Part 3: How To Ideate From Your Initial App Concept]]></title>
            <link>https://medium.com/@alliedcode/how-to-bring-an-app-to-market-part-3-how-to-ideate-from-your-initial-app-concept-fb74ee383050?source=rss-7e378ac6d77f------2</link>
            <guid isPermaLink="false">https://medium.com/p/fb74ee383050</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[ideation]]></category>
            <dc:creator><![CDATA[Troy Anderson]]></dc:creator>
            <pubDate>Wed, 11 Oct 2017 21:45:42 GMT</pubDate>
            <atom:updated>2018-03-16T23:16:33.730Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iBjfJgYq3NM_7eavF8Od-w.png" /></figure><p>In our last blog, we went over why it’s important to ideate from your initial app concept. Here’s how.</p><p><strong>1) Find Your Why</strong></p><p>Simon Sinek’s business best-seller, “Start with Why,” speaks to a need of the human mind. We understand any topic best when we first understand its purpose. Don’t try to explain to me white water rafting technique until I first understand why I might enjoy white water rafting. (It’s fun, it’s thrilling, it builds team spirit, it brings you deep into nature …)</p><p>So, to best understand your app, first understand and write down:</p><ul><li>Why you want to create it</li><li>Why it should exist</li><li>Why anyone — preferably millions of someones — will want to use it on a frequent basis</li></ul><p>Writing down these why’s will help you make them concrete and specific. Vague notions such as “I want to be rich” or “I want to change the world” won’t get you far.</p><p>Understanding why people will use your app will provide insights into what to features to include. It will give you the motivation you need to complete the app, and a rich story to tell to entice people to buy it. Don’t ask why only once. For each answer, ask why that is. Ask this 5 times per question. Seek to really understand why.</p><p><strong>2) Be Mister Rogers</strong></p><p>If you’re too young to remember <em>Mister Rogers’ Neighborhood</em>, which aired on PBS from 1968–2001 (the second-longest running children’s show after <em>Sesame Street</em>), suffice it to say that Mister Rogers was a nice sincere man in a sweater who gently instructed children ages 2–5 how to grow up without ever sounding like a bossy parent.</p><p>Mister Rogers is who you want to be while brainstorming your app idea: open, encouraging, creative, fostering. This is true when considering the ideas of your brainstorming colleagues (brainstorming works best in small groups), and even more true when considering your own ideas. The risk in <em>not</em> being Mister Rogers is that you limit your app’s potential, and fail to see the breakthrough idea.</p><p>As with young children, allow your brainstorming phase to continue until all ideas have been exhausted, and it’s nap time. Sleep on your ideas. Some will fade away like pleasant dreams. Others will grow stronger, and resist concerns about feasibility. Those are your winners.</p><p>When brainstorming starts to wane, add constraints. Contrary to how it sounds, constraints spur creativity. Constraints to consider:</p><ul><li>Require that the app include magic or fantasy</li><li>Require that the user interface cannot include any text</li><li>Require that the app only has one view or screen</li></ul><p>Can’t you hear Steve Jobs say, “Design a smart phone with only one button”?</p><p><strong>3) See It</strong></p><p>Large swaths of our brains prefer imagery over language. It’s been proven that literally “seeing” an idea gives you more belief and confidence in that idea.</p><p>So, just as it’s important to write down your why’s, it’s important when ideating your app to visualize its functions and uses with drawings or sketches. Start with an outline of the screen. If your app is for a smart phone, find a template online and print out copies to sketch on.</p><p>While you need some ability to draw, it doesn’t have to be pretty. Get your thoughts on paper so you and others can provide feedback. As long as you can recognize what you’re trying to show, you’re good.</p><p><strong>4) Don’t Let Me Get Too Deep</strong></p><p>As Edie Brickell &amp; the New Bohemians sang in “What I Am” (1988), “philosophy is a walk on the slippery rocks.” During ideation, it’s best to stay close to the surface level. Details bog down ideas; leave them for planning and execution.</p><p>When sketching your ideas on paper, use a fat pen. I like to use fat colored pens. The colors spur creativity while the fat tops keep me from getting too detailed, allowing me to stay high level.</p><p><strong>5) Take the Red Pill, But Stay Near Land Lines</strong></p><p><em>The Matrix</em> explored how anything is possible in the universe of coding. But while ideating your app, it helps to tether yourself to a few lines of constraint:</p><ul><li>Set a time limit, generally 1–2 hours</li><li>Set a group size limit, ideally 4–5</li><li>Clearly define (and picture!) your audience, and make sure all ideas serve that audience</li><li>Set a minimum and maximum number of ideas, say 5–25</li></ul><p>Just as in <em>The Matrix</em>, the world is made of many different perspectives. Group your users into “personas.” Describe what each persona would think, feel, say, and do in regard to your idea and solution. By considering each persona, you will see new requirements and may eliminate some unnecessary ones.</p><p><strong>6) Think Lean</strong></p><p>Ideate using a short feedback loop: generate ideas quickly, prove them quickly, repeat. Distribute your 10 best ideas among the members of your brainstorm group, with instructions to test them based on defined criteria. For example:</p><ul><li>Find 5 people complaining online about the problem that your idea solves</li><li>Find 3–5 apps already in the App Store that serve a similar (but inferior) purpose</li><li>Find 10 people voting for your idea in an online poll</li></ul><p>Separate the winners and losers, and repeat until you have your minimum number of ideas.</p><p><strong>7) Test It</strong></p><p>Once you have your best ideas, clean up your sketches, mock them up, and test them with your app’s eventual users. Again, they don’t have to be pretty. No coding is required — just get the idea across. When showing off the ideas, use your ears, not your mouth. Listen to feedback and write it down. Don’t explain or defend your ideas until you’ve gotten a lot of feedback. User confusion is the feedback you need to improve the idea. Ultimately, testing will tell you whether you on target, need to modify your app, or are ready to commence development.</p><p><strong>Conclusion</strong></p><p>“Give me six hours to chop down a tree,” Abe Lincoln said, “and I will spend the first four sharpening the axe.” Preparation up front for app development saves a lot of time and frustration later. Ideation is that preparation.</p><p><em>Originally published at </em><a href="http://bit.ly/2yg2PWt"><em>www.alliedcode.com</em></a><em> on October 11, 2017.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fb74ee383050" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[“How To Bring an App to Market” Part 2: Why Ideate from Your Initial App Concept?]]></title>
            <link>https://medium.com/@alliedcode/how-to-bring-an-app-to-market-part-2-why-ideate-from-your-initial-app-concept-6c5ad92a21b6?source=rss-7e378ac6d77f------2</link>
            <guid isPermaLink="false">https://medium.com/p/6c5ad92a21b6</guid>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[ideation]]></category>
            <dc:creator><![CDATA[Troy Anderson]]></dc:creator>
            <pubDate>Mon, 02 Oct 2017 14:28:49 GMT</pubDate>
            <atom:updated>2017-10-30T17:27:58.232Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/742/1*hR8kp1MX4fg4KW-7QNjKsQ.png" /></figure><p>With more than 1.5 million apps in the app store, only 0.01% of apps are in the top 10, and <strong>only 0.1% make it into the top 100</strong>. Even for large app developers, the odds are against you.</p><p>People approach me daily with app ideas they want to develop. Most have met a single criteria: a generally identified need. But to be successful, they need to solve real problems, and be compelling enough for people to change their routines.</p><p><strong>What separates a best-selling app from average, forgettable-amongst-millions apps is the creator’s ability to ideate the app beyond its first concept.</strong></p><p>I’ll use one of my own apps as an example. Over40 has sold half a million units in the App Store and has been in the top 10 grossing utility apps. It’s a simple app that combines a flashlight with a magnifying glass. It produced a significant return on investment.</p><p>The market need for the app is found in its name. (Finding the right name for your app is another reason to fully ideate the concept.) As human eyes age, the pupils become less responsive to changes in light. Eyes over 40 need more light to focus.</p><p>In addition, eyes over 40 develop <em>presbyopia</em> — farsightedness — that results from a hardening of the eye lens. The correction is reading (or magnifying) glasses.</p><p>Combining two features — flashlight and magnifying glass — into a single app may have been enough to make Over40 succeed. But when we fully ideated the concept, we recognized that the occasion when most people will feel the need for this app is when they try to read restaurant menus.</p><p>Most “fine dining” restaurants dim their lights at night. It’s more romantic. But lighting that makes the person sitting across from you look sexier can make the menu indecipherable. And asking the server for a large-print menu is distinctly <em>un</em>romantic.</p><p>Having recognized that Over40 would be used most often in restaurants, we added a tip calculator, because it’s also unsexy to ask your date what 15 percent of $84.75 is. (Especially if your date thinks you should tip at least 20 percent.) And, recognizing that many dinner dates are between friends and not romantic partners, we added a feature that splits the tip.</p><p>That might sound like a small change, but the impact was dramatic: Over40 went from yet-another-flashlight-app to “the tool I use in restaurants.” Its purpose was transformed from mechanical (light + magnification) to solving a persistent problem in its users’ lives.</p><p>Apple’s interfaces also are designed for users’ lifestyles. That’s why Over40 became a featured app in the App Store, which led to its sales success.</p><p>Having established your need to fully ideate your app, we’ll next outline how to do so.</p><p><em>Originally published at </em><a href="http://bit.ly/2xSudcA"><em>www.alliedcode.com</em></a><em> on October 2, 2017.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6c5ad92a21b6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What’s the Idea? Top 10 Ways To Generate App Ideas]]></title>
            <link>https://medium.com/@alliedcode/whats-the-idea-top-10-ways-to-generate-app-ideas-23a891bd0594?source=rss-7e378ac6d77f------2</link>
            <guid isPermaLink="false">https://medium.com/p/23a891bd0594</guid>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[ideation]]></category>
            <dc:creator><![CDATA[Troy Anderson]]></dc:creator>
            <pubDate>Fri, 29 Sep 2017 17:50:31 GMT</pubDate>
            <atom:updated>2017-09-29T17:50:31.471Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*mmZl2-KId1wH0N-A.jpg" /></figure><p><strong>10) Improve Existing Job Roles</strong></p><p>Remove steps and increase efficiency of an existing job role. App examples:</p><ul><li>Instagram simplified retouching and sharing photos</li><li>Twitter replaced newswire services by enabling private citizens to announce news</li></ul><p>Can you improve function that you perform or buy regularly?</p><p><strong>9) Focus on Problems</strong></p><p>There’s an old saying in sales: “Find the pain, and push it.” People want to buy fixes to problems that annoy them, frustrate them, or waste their time and energy. When you find pain points, solutions are often quite obvious. App examples:</p><ul><li>Evernote integrated, centralized, digitized, and prioritized note taking</li><li>Pocket makes a list of things to remember to read online</li></ul><p><strong>8) Examine Your Passions</strong></p><p>Work on what excites you. This may open up new concepts, or highlight an area where you can add value. Existing apps don’t mean there’s not space for yours — in fact, they may prove the market appeal of your idea.</p><p><strong>7) What You’re Good At / What You Know</strong></p><p>Leverage your skills and knowledge. You may have unique knowledge, or can use your skills to address an existing problem. For example, Mint.com leverages your existing knowledge of the financial industry, and adds value from there.</p><p><strong>6) What Already Exists</strong></p><p>There is nothing new under the sun.<br> — King Solomon</p><p><em>An original idea. That can’t be too hard. The library must be full of them.<br> — </em>Stephen Frye</p><p>We tend to glamorize originality. If you focus on a niche, look at what already exists. There’s often room to improve it, or create meaningful variations. Why should software be any different than music?</p><p><strong>5) Go Around the Room</strong></p><p>Gather a small group of trusted friends and advisors, and take turns voicing an app idea. (This can be a fun drinking game, as long as you keep the pace of rounds slow.) Each person offers only one idea — no matter how crazy or outlandish — and tries to sell it to the rest of the group in a maximum of one minute. Keep going around until all ideas have been exhausted. Oh, and designate a note-taker — preferably someone who likes sobriety.</p><p><strong>4) Mind Mapping</strong></p><p>Draw any thought/idea/problem in the middle of your mind map. Next, dig into that thought/idea/problem and break it into other ideas, drawing them out in any direction. If anyone contributes a totally different idea, draw it on a new canvas, or in a separate area. Let the ideas flow. it doesn’t matter if the relationships aren’t correct. Your map should not be neat or pretty. It should look like all of the ideas have fallen out of your head onto paper.</p><p><strong>3) Idea Wall</strong></p><p>Use Post-it notes in a similar way to mind mapping. Find a space on a wall or large white board, write ideas on post-its, and stick them on. Stick similar ideas close to each other, and use the same color of Post-Its for similar ideas. You end up with idea clusters. Feel free to move ideas around, but avoid the temptation to arrange perfection. Take photos of your idea wall so you refer back to them. Number the Post-It to make it easier to refer to them.</p><p><strong>2) Google It</strong></p><p>Have a seed of an idea, and want to expand it? Google makes a great discovery tool. Don’t dig into details. Instead, discover related problems, ideas. Find discussion forums and blogs on your topic. Look for common themes, gripes, problems. Ask questions to kick off discussions that expose pain points.</p><p><strong>1) Lean Ideation</strong></p><p>Lean ideation generates ideas and proves their worth quickly, then repeats the cycle. Using an idea wall, generate 10 ideas in 10 minutes or less. Assign each idea to a team member, with a deadline to prove it. Proof criteria can include people complaining online about the problem the idea will solve, and existing similar apps. Glean the ideas that pass the test, then repeat the process until you obtain your target number of ideas.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=23a891bd0594" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>