Do you know what many visionary tech entrepreneurs have in common, besides business acumen, persistence, commitment and confidence in their own tech genius?
An inability to properly and clearly formulate their project idea or concept to those who’ll actually be working on bringing them to life!
Of course there are exceptions, just as in anything, but based on my seven plus years of experience working in IT, most of our future mobile product creators fail to create clear and well-structured mobile app development specifications. Otherwise we at Intersog wouldn’t receive so many chaotic app specs, sometimes resembling an essay by a college fresher (though some app owners are indeed college freshers) or notes from an insane asylum rather than a set of technical requirements.
You may object that all idea hamsters are creative by nature and creativity doesn’t always equate with an orderly approach. The problem is that a poorly written app development spec is likely to prevent you from getting your mobile product on time, on budget and matching your initial vision, and from correlating your actual expenditures with a development budget and creating an environment of a shared product vision with your development partner or team.
The technical specification generally defines requirements needed to fulfill the development contract, so when you’re unable to supply your future app development provider with a clear vision of the product and how it will interact with users and systems, be ready to face overheads and delivery issues at post-release stages.
Service providers literally hate getting specs that lack important details, such as the app’s target audience or the server collaboration or the proof of concept. Translating the messy, fragmented or cumbersome narratives into the technical documents requires additional efforts and time and both are very expensive these days, as you know. My former employer was so pissed off at receiving raw and unclear specs that it launched a series of workshops to teach companies how to create proper and well-structured mobile development specs. And believe me – those workshops were in a very high demand and came to be a great source of additional revenue!
But making a killer mobile app development spec is not so difficult at all, so why waste money on them? Just stick to the suggested sequence below while writing your next big hit app’s spec and you’ll be able to properly envelope your ideas and vision for your service provider’s sake.
- First off, explain all definitions, acronyms and abbreviations to be used in the document (this can be done as a last step when writing a spec, but should always be placed on top of the document)
- Describe your app’s goal
- Describe your app’s target audience
- List and prioritize all mobile platforms your app is intended for
- List and prioritize all devices and OS versions your app is intended for
- List all technologies that should be used for building your app (I suggest you always make your own research before getting provider’s response and asking for suggestions)
- List major milestones (from analysis, prototyping, and pre-release to app store placement), their due dates and/or desired timeframe for proof of concept/delivery
- Specify your project’s budget
- Usability (screens, view modes, menus, etc) and UI
- Social media integration (list all social media channels you want your mobile app to interact with)
- App’s collaboration with the server, including detailed description of the app-server interaction mechanism, protocols and likewise data
- Data caching for offline work if required
- In-app purchasing if applicable (specify what type of content will be sold to users inside the app)
- Geo-location services and push notifications
- Printing functionality
- Compatibility / sync with e-commerce engines, internal CMS and other systems
- Here you should specify who will do the graphics design part – your in-house designers, freelancers, a subcontractor or a development provider. In any case, a design specification should be created separately and integrated into the app development requirements document.
- Provide your market research details and links to / description of all rival / similar apps
- Express your concerns, limitations and special wishes for the service provider to have a complete picture of your future app and its role in the marketplace
- List all points of contact within your organization and briefly describe your vision of how communication between your company and your app developer should be handled throughout the project
Also remember that a killer mobile app development spec should be truthful, unambiguous, consistent, verifiable, modifiable and traceable. Try to stay away from generic requirements such as “the app should never crash” or “the app should respond quickly to a user query” and provide quantitative requirements instead such as “each button push should provide a response within 100 ms”.
Be sharp, crisp and up to the point and you’ll gain maximum value from providers’ responses to your RFP!
User Interface Design with Sketch 4
Researching UX: Analytics
Rails: Novice to Ninja
Designing UX: Forms
- 1 Picking the Brains of Your Customers with Microsoft's Text Analytics
- 2 6 Things to Know Before Launching Mobile Apps on the App Store
- 3 Is It Possible to Write and Run PHP Code on an iPad?
- 4 Build Your Own Dropbox Client with the Dropbox API
- 5 There Are More Virtual Reality Headsets Than You Realize!