NaviGap Development Costs

NaviGap Development Costs:

The primary factors that we see as influencing the development costs of NaviGap include:

  1. Monetisation Model
  2. Platform
  3. Functionality
  4. Design
  5. Research
  6. Developer

1.Monetisation Model

It would be easier and more straight forward to create an app that is simply sold for a fixed, upfront price as opposed to one with In-app purchases that will require continuous updating to the software. We have decided on a blend of models that will include in app purchasing therefore long term costs of development need to be factored in.

2. Platform: Android Or Apple

iphone mapIt is possible to build an app that is accessible on a number of devices: iOS (iPhone and iPad), Android, Windows Phone, the Web or one that can be used on all of them. The price of development will vary accordingly. At this stage we are only considering mobile apps however, and therefore our options are either Android or Apple. We have determined that our app is to reach a demographic of 18-25 years olds so JAMR researched which platform would best suit this.

Image from blog.mobiscroll.com.

Each one of the aforementioned platforms requires a particular programming language, different development environments and programming models based on platform-specific APIs. For example, developing applications for Android requires Java, while developing applications for iOS requires Objective-C. It is apparent that, if a company decides to support both Android and iOS platform, there is a constraint to maintain two versions of a single product: one version implemented with Java for Android and a second version implemented using Objective-C for iOS. Mobile cross-platform tools (CPTs) provide an interesting alternative to native development. Cross-platform tools aim at sharing a significant portion of the application codebase between the implementations for the different platforms. This can drastically decrease the development costs of mobile applications. (Willocx ,Vossaert , Naessens, 2016).

JAMR intends to use a CPT to generate an app for both IOS and Android.

 

3. App Types & Functionality

The technical specifications of the app will be the single biggest factor in its cost. App types down into the following four categories:

  1. Table/List – designed primarily to display a relatively simple collection of information
  2. Database – designed to allow users to find, sort, and display data from data sets
  3. Dynamic – designed to cooperate with other platforms and software via APIs.
  4. Games- designed to be dynamic and have advanced features.

The more complex the functionality, the expensive the corresponding development cost will be. Quotes will need to be solicited from multiple developers, however, JAMR plans to develop the app ‘in house’ using our teams software development skills thus reducing the cost of development.

 

4. Design:

The design is an important feature of the App, particularly in terms of attracting a user to the initial download since customers are attracted by an icon and/or design. Similarly, design can make them want to use the app more, NY Times 2015.

A compelling design generated from a proven design team with a consumer-tested portfolio, could be very expensive. JAMR need to budget and prioritise based on the young person target audience who potentially are very design sensitive, therefore priority will be given to a high end design.

 

  1. Market Research:

The traditional questionnaire survey incurs a great human and financial resource. Whereas an online survey system could immensely cut the costs of questionnaire printing and labour in terms of service fees for interviewers, travelling expenses and data entry fees with a fixed cost will be paid that includes questionnaire design fees, network expense and data analysis service fees.

Other advantages of web-based questionnaires are:

  • Automation and real-time access.  Analysis is easier, and available immediately.
  • Convenience.  Respondents can answer questions when they want.
  • No interviewer.  No influence from the interviewer, means less bias.
  • Target PopulationThe sample may prefer just online surveys.

Therefore, a web-based questionnaire could replace the traditional paper questionnaire with minor effects on response rates and lower costs, potential disadvantages being a lack of respondent cooperation in terms of internet uses receiving lot of feedback requests, and the lack of interviewer to clarify respondent queries could mean that data collected is less reliable. (Hohwü, 2013).

 

6. Developer: Freelancer vs Agency

Different apps vary widely in developmental cost and there are 3 basic categories of developers you can choose from:

  1. Freelancer – affordable option
  2. Small agency – specialists in specific areas
  3. Large agency – big brand guarantees

Clutch surveyed representatives from 12 leading mobile application development companies to determine cost ranges of building an iPhone app and the key variables of cost and found that the median cost  range is between $37,913 and $171,450, but could be as much as $500,000.

NaviGap however will be using JAMR’s ‘in house’ software developer on this project.

 

Hohwü, L., Lyshol, H., Gissler, M., Jonsson, S. H., Petzold, M., & Obel, C. (2013). Web-Based Versus Traditional Paper Questionnaires: A Mixed-Mode Survey With a Nordic Perspective. Journal of Medical Internet Research15(8), e173. http://doi.org/10.2196/jmir.2595

Personas

33214467092_6b7ddb717a_o

We have outlined in detail our goals and incentives, and especially mentioned our focus on the user, so now it is reasonable to prepare persona portraits to encapsulate our typical audience representatives.

In any platform development and design, it is necessary to think about who, how and why will use your product. Taking into account habits, wishes, concerns of our personas will drive the design vision and functionality of our app. We take into consideration the ‘use activity’ in order to compile our development requirements.

Behind our user interface is the understanding of real-life interfaces to support the process of traveling. We believe in a niche targeted approach so that best suitable scenarios fit a prefixed user group of a certain type.

In their academic research Viana G., Robert JM. (2016) give a definition for personas: they “are “hypothetical archetypes of actual users through which designers can develop a precise description of [the] user and what he wishes to accomplish”. In their paper, they conclude that building personas is helpful for designers to visualise and summarise functionalities and features of a product that is to be developed. Although, they note that it should be done in conjunction with real user usability testing. That said, our persona portraits represent a concentrated view from different angles of our potential users.

Our personas were generated from the thorough review of forums and related social networks followed by classification and critical analysis.

First, we brainstormed persona types and came up with three portraits: an undergraduate first-year student (18-22), a mature student (22-25) and a commercial partner. Our user experience team talked to representatives of these user groups (at university, book stores) acquiring tons of data and identifying motivations, worries, past experience, characteristics, and needs.

Second, our team collectively gathered, sorted out, systemised and classified all the data to produce objective portraits with a rich description of each persona.

Here are the results:

Screen Shot 2017-03-18 at 15.00.56 Screen Shot 2017-03-18 at 15.03.22 Screen Shot 2017-03-18 at 15.04.03

We hope that such user-centric design will elevate our product value to the highest level.

All images are used under CC license.