iPhone Application Definition

To create a five-star app, we need to understand your product idea as thoroughly as possible. The questions here are a starting point for this understanding. If you want an estimate on your project, you will need to have answered all of these questions that are relevant to your idea.

We aren't picky about the format. You can provide the answers to these questions in a Word document, Powerpoint, Excel, text, or web site. However, it needs to be in writing, because nothing forces you to think about an idea like writing it down.

At any time, feel free to contact us for assistance!

Note: It is just as easy to develop apps for the iPod Touch as it is for iPhone. We say "iPhone" throughout because it gets tedious to say "iPhone or iPod Touch" everywhere.

About Your Users

In describing your users, don't say "people who own an iPhone." Think hard about it - there isn't a single app on the AppStore that appeals to everyone. Even a universal app like Safari isn't used by everyone who owns an iPhone.

Product Consumers

Describe the typical or most likely person who will be using your product. For example:

• If it is a game, is it geared toward 20-somethings? Men? Women? Children? People who like puzzles? People who like tower defense games?
• If the product is a utility application, who will be using it? Why does this person need it?
• Do you assume some level of knowledge of your users? For example, if it were a tool for musicians, do you assume they are beginners or experienced musicians?

Use as much detail as possible. A great way to do this is to create a fictional person and describe them in as much detail as possible.

Product Administrators

If your product includes a server-side component, it may require some system administration.

Describe your system administrators in the same way as for consumers.

Indirect Users

Some products are built for more than just end users. For example, a product for restaurant customers might also include restaurant managers as another type of user. Describe any indirect users related to your idea.

App Users versus Customers

In most cases, the customer is the same as the app user. However, this is not always the case. Free applications that are geared toward some other service might have customers who are different than the actual end user. A well-known example is Google. Google has two primary users – those doing search on their site, and advertisers, who are their real customers. These two groups have completely different goals when they come to Google.

About Your Product

Product Goal

Describe how your product will delight your customers.

• What is your product trying to achieve for your end user?
• Is it solving a need for them?
• Is it entertaining them?
• Challenging them?
• Is it trying to make them laugh?
• If you could describe your product as one feature, what would it be?

Product Description: To App Users

Describe your product as you will on the Appstore in 750 words or less (usually much less). You will need to do this anyway when you submit your application to the AppStore, so you may as well think about how you will present it now. For guidance, browse applications on the AppStore to see how others are describing similar products.

Product Description: To Customers

If your customers are different than your app users (see above), describe your application as you would to your customers.

Use Scenarios

Describe in narrative form how someone will use your product. Tell a story using a fictional person. Use as many scenarios as necessary. If you have multiple types of users interacting with your application, describe a scenario for each type of user.

Design Considerations

We will work closely with you to develop a great design for your product. However, you may have already thought through how it might work on the iPhone.

Think Mobile

Consider the context in which your users will use your iPhone application. Even though the iPhone is a powerful small computer, the mobile environment is fundamentally different from a desktop computer.

• Typically users will be away from their computers, possibly traveling or in a meeting.
• They probably want to use your application to get quick access to some key feature or piece of information.
• Your users will often be in a hurry, constantly interrupted by the events around them.
• Even if they are trying fill in time on an hour-long train ride, they will be interrupted by announcements and lack of network coverage.
• Is this iPhone application supplementing an existing web site or application? Does this desktop based user experience need to change with the introduction of your iPhone based service?
• If the iPhone app needs to to interact with a server side component, do the APIs exist already, or do they need to be developed? If they need to be developed, do you want us to do the server-side API development for you?
• Does your application use location based services? If so, what accuracy does your application require? What should the user experience be when GPS is unavailable or accuracy is poor?
• If your application requires network connectivity, how should it behave when the connection is lost or too slow for proper use?

Design thoughts and ideas

We don't require any of these, but if you have already thought about it, it will help understand your idea. Include any of the following:

• What are the key views or screens that your users are most likely to want to access quickly when they are away from their computers?
• Product Sketches (any form is okay – even hand-drawn sketches)
• List of screens in the application. For example, menus, forms, etc.
• Preferences the user will be able to set.
• Forms and data that the user would have to enter.
• Screen shots or links to similar applications on the web or other devices.

System Architecture

Answer the following questions only if you have an existing system that will be integrated with your iPhone application. If you plan to create a new server-side system, we can work with you to arrive at an optimal architecture.

• Will your product interact with an already-developed server-side component? If so, describe it.
• Describe the high-level interaction between the iPhone and the server. If your application needs to communicate with other iPhones or a desktop computer, describe your requirements as well as the interactions.

Competitive Analysis

List your competitors. If you don’t currently have competitors, you can safely assume that businesses with similar products will be your competitors soon. Everyone is thinking about the iPhone right now. You can also assume that if you create a great app, others will copy you and try to improve on it.

• If your product is creative, such as a game, list similar iPhone games. Why will yours be more fun or challenging?
• If your product delivers a service in a new way, then list competitors who provide the service using existing mechanisms.
• List your competitors' web sites, and name on the AppStore if any.
• Describe competitors' prices or business models.
• How your product will be different from or superior to your competitors'?

Business Model

• How will your idea make money?
• If it is simply going to be a non-free downloadable application on the AppStore, how much do you plan to charge?
• How did you arrive at this price?
• Have you considered an advertising model? Why or why not?
• Have you considered a free version as well as premium version? Why or why not?
• How big is your target market?
• What percentage of iPhone users do you think will want or need your app?
• If you have some other business model such as advertising, separate service, etc. describe it.
• Are there any major brands who might be interested in sponsoring a free version of your product?

Post-launch success

We can help you post-launch by providing tools for tracking app usage, integrating with social networking sites, or building a web site for you.

Marketing

• When do you plan to release the app?
• How will you get the word out about your app?
• Are there any events coming up that might tie in well with the launch of your app?

Usage Tracking

• Given your product idea, your customers, and your business model, how will you measure success?
• What might your application track with regard to usage that will help you measure success and improve your product?

Improvements

• How will you improve your product in the next version?
• Another way to think about it: what could a competitor create that would scare you?