This document provides guidance on evaluating the technical feasibility of a mobile app idea. It discusses assessing an idea based on required data, integrations with third parties, need for backend services, and competitive landscape. Key questions are posed in each area to determine what is needed to realize the idea technically and whether it is worth pursuing. Integration risks with major partners like Twitter and Netflix are also highlighted.
1. Evaluating Your App Idea
From a Technical Perspective
Vance Lucas
http://vancelucas.com
2. Target Audience
ā¢ Limited technical knowledge/
experience
ā¢ Anyone interested in everything that
goes into making apps
ā¢ People who have app ideas, but donāt
know who to talk to or where to start
3. Who are You?
ā¢ Vance Lucas
ā¢ http://vancelucas.com
ā¢ Twitter: @vlucas
ā¢ Brightbit (local dev. shop) until 2014
ā¢ Consulting/Freelance afterwards
ā¢ Now full-time at NetSuite
6. This IS
ā¢ Pre-market validation of idea itself
ā¢ Technical feasibility determination
ā¢ āIs this idea even possible?ā
ā¢ āIs this idea worth pursuing?ā
7. This is NOT
ā¢ Good / Bad idea judgement
ā¢ āYour idea is [awesome|terrible]ā
ā¢ Determination of success
ā¢ Market validation
10. ā¢ What is the idea?
ā¢ What problem does it solve?
ā¢ How do users solve this problem
currently?
ā¢ How will your app solve this problem
better?
Story: App Idea for Take-Out Menus
12. ā¢ Does my idea require data or
information that I donāt have?
ā¢ How can I get this data?
ā¢ What will it cost (time + money)?
ā¢ How hard is this data to get?
ā¢ Will I own or control this data?
Story: App Idea for Road Trip Guide
14. ā¢ Does this require integration with a
3rd party (Twitter, Facebook, data
source, etc.)? How deep?
ā¢ Does it cost money?
ā¢ What are the risks in integrating?
Story: App Idea to Cancel Credit Cards
17. ā¢ Is a central database or web service
required for your app to function?
ā¢ Are you going to have a user login?
ā¢ Will any data sync across devices?
ā¢ Is any content āsharedā with, or
ādiscoveredā by other users?
ā¢ Is there any content not stored only
on a single userās phone or device
18. You Need an API!
ā¢ Whole separate (large) project with
tight integration into your app
ā¢ Recurring costs? (domain, hosting, etc.)
ā¢ Risks? (security, availability, etc.)
if you answered āyesā to any of thoseā¦
21. ā¢ Are there any competitors?
ā¢ If so, how many? How big are they?
ā¢ Good ratings? Any complaints?
ā¢ How is your idea diļ¬erent?
ā¢ What is your unique value
proposition
22.
23. Market Analysis
ā¢ How big is the market?
ā¢ # of apps in this category?
ā¢ # of searches for app keywords?
ā¢ # of downloads of competition?
26. ā¢ How will this make money (ROI)?
ā¢ One-time purchases or subscription?
ā¢ Free with ads or in-app purchases?
ā¢ How does this align with costs?
ā¢ Remember 30% cut for app stores
ā¢ Does it even need to make money?