Custom Development

A picture is worth a thousand words and QuickMobile's Smartphone applications, mobile websites and text messaging campaigns speak volumes about our constant pursuit of quality and drive for great design, ease of use, device performance and end-user engagement.

On the surface mobile application design and development may appear to be simple, however understanding the "mobile context" is not immediately obvious. Mobile users expect immediacy, relevancy, personalization and convenience – the ultimate mobile experience is vital to the engagement of the user and the perception of the brand.

Mobile application design and development may appear on the surface to be simple, however understanding the "mobile context" is not immediately obvious. Mobile users expect immediacy, relevancy, personalization and convenience – the ultimate mobile experience is vital to the engagement of the user, repeat usage and the overall perception of the brand.

QuickMobile Custom Solutions and Development Methodology

QuickMobile provides its customers with mobilization strategy consulting, SmartPhone application development (internal systems and consumer applications), licensed application software and text messaging campaigns.

In addition, QuickMobile's QuickStart Platform™ enables companies to "mobilize" their business services quickly and provides real-time update capabilities, creating and maintaining a mobile audience and rapidly monetizing their mobile applications and services by providing:

1. Easy integration of data or content residing in clients' in-house solutions, website or CRM with the QuickMobile delivery platform, streamlining the entire mobile integration process
2. Content management component (CMS) to provide real-time conversion of all kinds of existing content or data changes into mobile-ready content including text, audio, graphics, photos, video and other wireless formats, and including the facility for the customer to make real time changes
3. Mobile analytics to help understand end user behavior and preferences
4. mCommerce integration
5. Connectivity to any mobile phone (device agnostic)
6. Mobile advertising

Client Engagement and Development Methodology

Our Client Engagement Process includes the following major milestones:

• Scope and definition of application (this proposal brings much of this together)
• Prototype (may not be required)
• Technical specification
• Storyboarding of user interface (GUI)
• QuickStart Platform™ Interface design and Web Services Integration
• Application development
• Content and Third Party integration
• QuickMobile QA
• Focus Groups and External QA
• Client QA – Feedback and Change Orders
• Client Sign off
• Third Party Approvals if necessary (such as appStore approval process)

Agile Software Methodology

We have adopted the Agile software development methodology and our development processes follow these guidelines. Agile software development refers to a group of software development methods based on iterative development, where requirements and solutions evolve through collaboration between organized cross-functional teams. The term was coined in the year 2001 when the Agile Manifesto was formulated.

Agile methods break tasks into small increments with minimal planning, and do not directly involve long-term planning. Iterations are short time frames ("timeboxes") that typically last from one to four weeks. Each iterative phase involves a team working through a full software development cycle including planning, requirements analysis, design, coding, unit testing, and acceptance testing until a working product is demonstrated to stakeholders.
This approach helps minimize overall risk, and lets the project adapt to changes quickly. Stakeholders produce documentation as required. Single iterations may not add enough functionality to warrant a new market release, but the goal is to have an available release at the end of each iterative phase. Multiple iterations may be required to release a product or new features.

The Engagement Process

QuickMobile's engagement and development process includes the following formal steps:

1. An initial proposal will form the basis of the Requirements Document, our estimated project time lines, and pricing
2. The customer provides a deposit following the decision to contract QuickMobile and signature on the proposal documents
3. QuickMobile's Project Manager will complete the formal and final Requirements Document, approve the functional specifications and establish project Milestones and Responsibilities that are mutually agreed to at that point.
4. Apps and mobile website will be delivered according to the project development schedule
5. The customer is consulted on an agreed timeline (usually weekly) to monitor progress and approve application layouts, design, navigation and look and feel.
6. QuickMobile may provide a prototype

Requirements Document

The Requirements Document outlines the specific functionality needed and includes User Stories (case studies). The result of these requirements specifications is a Product Definition Statement that QuickMobile produces as a guideline for the Design Phase.

Design phase

QuickMobile will produce the following:

1. GUI Layouts

- Mock-ups based on the Requirements
- User Testing or Focus Group Testing
- Customer signs off on GUI

2. Data Integration

- Discussions with the Customer on data stream connections and update requirements

3. Sprint Planning

- Development tasks identified, number of sprints required, development tasks organized for each sprint

Development Phase

When this phase starts, the customer and QuickMobile have agreed to the final Requirements and the Design of the proposed solution, decided on how changes are authorized and by whom, and have signed a Requirements and Design Mutual Agreement document.

The following are the major steps in the Development Phase:

1. Customer feedback on layouts incorporated into design
2. Sprint 1 requirements

- Alpha version completed
- Data Integration issues resolved

3. Retrospective #1:

- Review Sprint
- Identify any roadblocks
- Reorganize Sprint 2 goals
- vAlpha Build

4. Same procedure for following Sprints

Testing and Quality Assurance Phase

This phase includes rigorous testing of the functionality, interface and navigation, data integrity and updating, personalization and user settings and overall device performance metrics.