Bridging The Mobile Divide

359’s Mobile Application Development Process

359’s mobile platform will require integration with the customer’s current or future online site, backend processing and customer deliverables. As with all our customers we expect to work closely with the customer’s engineering and marketing teams.

359 uses a phased approach when developing a 359 mobile application. 359 and the client are integral parts of the process which consists of the following six phases:

1. Project Definition

2. Application Structure

3. Visual Design

4. Application Development

5. Testing

6. Release and Maintenance

Each phase consists of several steps or tasks that must be completed to ensure a successful product. The initial phases of the process allow 359 to collaborate with the client to determine essential items such as the target audience, brand goals, content source, technical requirements, and timelines. In subsequent phases, 359 and the client produce, test, and release the actual product components. The phases are intended to get from idea to implementation quickly by using the 359 platform to eliminate the usual technology and infrastructure worries associated with mobile application development.

The most critical step in the application development process is creating an accurate project definition. The definition should include the vision and goals of the product, the intended audience and technical requirements, and the project and maintenance plans.

1. Client Interview – documents the purpose of the project, target audience, branding/perception goals, content source, initial technical requirements, usage, load, and support expectations.

2. Project Brief – is a one-page document derived from the client interview that clearly states the product vision, goals, audience, competitive advantage, and target launch date for the product.

3. Audience Profile – defines imaginary users of the product including demographics, technical profile, top three user goals, and top three business objectives for the product.

4. Technical Requirements – specifies the range of devices to be supported, the source of content, data and business logic, the expected usage and the desired server response times.

5. Functional Requirements – define the functionality of the product based on the client’s expectations.

6. Project Plan – establishes the timeline for deliverables and the tasks and responsibilities for each phase of the project.

7. Maintenance Plan – documents how and who will update the product and provide user and administrative support.