How We Handle Customer Requests for App Development

When a client comes to us with a vision for the kind of application they want, we make sure that we can communicate clearly how we can help them get the app developed, how long it would take and the costs it would incur. From the get go, we strive to understand the exact specifications of the client through drafts (called wireframes) and flowcharts.

Once the documentation is ready and agreed by both parties, we move into the designing and development phase. In this post, we’ll take you through a sample consultation.

Step 1: Overview of the Application

The first slide of our proposal briefly explains in words what the purpose of the application is and what goals it wants to achieve. These are usually presented in bullet points so the client can quickly go through them.

For our sample case, the overview of the application could look like this:

• A Facebook application that lets users create custom greeting cards the size of cover photos.
• The application would allow users to choose backgrounds, borders and add custom text.
• Users will then select friends to whom they want to send the greeting card.
• The greeting card would be shared on their friends’ Facebook Wall from where it can be swapped as a cover photo.

There is no superfluous detail, no technical jargon and no mentions of back-end work in the overview. It has to be simple, to-the-point and clear enough for a layman to understand.

Step 2: Application Flowchart

The second slide of our proposal contains an application flowchart which is simple, yet detailed enough to help the client understand how the application would work behind the scenes. We mention any special interfaces that the app will interact with and the steps the user will take.

Step 3: Wireframes

The slides that follow the flowchart show wireframes of the screen flow of the application. They give the client a good idea of how the user will interact with the interface of the app.

Designing wireframes is helpful to ensure that both parties have sound knowledge of where the project is headed. It helps the client visualise what the end result will look like even though wireframes are neither the final design nor the final layout. They’re simply rough sketches that explain the flow of the application.

Step 4: Project Timeline

Next, we break down the project timeline according to each of the following phases:

• Documentation
• Design
• Database design
• HTML design
• API integration
• Implementation of admin features (if any)
• Testing and debugging
• Deployment
• Analytics

This gives the client a good idea about how many days or weeks each process is going to take. It establishes credibility and trust and lets the client know that we’re not just throwing a random number. A project timeline also helps the client keep track of the progress of the project. They are informed about what to expect at what day and can compare the progress with the timeline we provided them.

Step 4: Cost

We then list the costs for the project. We calculate costs based on the features of the application and the kind of resources it will utilise. It also depends on the creative design of the app – whether it is simple or time-consuming. The general complexity of the application’s functions and the time it would take to develop also contribute to the costing of the project.

Conclusion:

This kind of proposal helps us establish trust with the client and also ensures that there are no design overhauls mid-way through implementation. At each phase, we meticulously recheck with the client if the application is developing according to their needs so that changes can be made then and there. If you’re looking to develop a Facebook, web or iPhone app, you can contact us for your free consultation today.