Wednesday, April 7, 2010

Mobile Applications - Where do I begin

Many of our customers come to us with some concept about mobile application and they tell us that we have some idea what next I should do?

We suggest to customer that a detailed requirements specification is the key to deliver software in accordance with customer's needs and ensure application usability and security. Our mobile developers meet the challenges of this phase to resolve our customer's business objectives.

Here are the steps required

1. Mobile Functionality Requirements: After the completion of the initial preliminary application study, it is necessary to identify and define the application’s functional and non-functional requirements. A high-quality requirement specification ensures the competitiveness of the application by guaranteeing that the key features of the application respond to actual and existing market demands and user needs.

Note that at this phase, you also effectively decide what the application should not be able to do. That is, you determine which requirements are valid and feasible and which functionalities will not be included in the application.

The requirement specification should include the following:

  • Definition of all the required functional and non-functional qualities of the application. It should answer the basic question "What does the application do?".
  • Lists of application dependencies.
  • Input for all subsequent project phases.
  • Input for marketing purposes.

2. Defining Scalable UI: While ensuring application scalability to different display resolutions and orientations may require additional work in design, implementation, and testing, it has clear benefits. An application that is built to support scalability can be installed in a wide range of current and future target devices, making the potential customer base for the application significantly larger.

Scalable application development reduces effort from the post-production phase, as the need for making application variants for secondary target devices is reduced. If the same version of the software is not directly compatible with a secondary device, the post-production work is likely to be easier and faster for an application that has been developed with scalability in mind.

3. Target Mobile Devices: Discuss with customer in the target mobile devices. This is to ensure that right development platform is selected for the mobile application development.

4. Security requirements: Defining good application security requirements may be difficult. Security requirements may be more straightforward to express by describing the threats the application is likely to encounter. The relevant threats can be considered as negative use cases that should be avoided. They can describe different scenarios and interactions that must be prevented in the application design.


Semaphore has expertise in providing various types of services including SEO Services, Software Development and Mobile Website Development services. Our skilled Mobile Web Developers have proficiency in iPhone Application Development, iPad App Development, Blackberry Application Development, and J2ME Mobile Application Development.

No comments: