How we take your app from concept to reality

We get requests of different shapes and sizes. Sometimes it's just a concept, sometimes it's a low-fidelity wireframe or pencil sketches. Sometimes it's a colourful wireframe built in Figma. Sometimes it's an existing application that we need to remake or take over. Sometimes it's an amazingly large spreadsheet that we need to piece together and convert into a web application.

Over the course of a few years building apps, we've dealt with loads of different scenarios and come up with a robust and fail-proof process that works for all complexity levels.

Step 1 — Client Kick-off

The first step after signing a new project is to prepare as much as possible ahead of kick-off. We share a checklist of the type of access we need. We have a large list of questions about the app. This is where we fully understand your expectations, collect all your requirements and identify any roadblocks.

Step 2 — Internal Kick-off

The requirements are communicated in detail to the development team so everyone is on the same page. We chalk out an implementation plan. What needs to be done by who and when.

Step 3 — De-risk Sprint

We occasionally come across features or integrations we haven't used before. We need to test these areas first to completely de-risk the app. Questions like, can we handle this feature, can we embed this widget, can we pass that webhook, etc. need to be answered to avoid any surprises.

Step 4 — Wireframes

We always prefer some kind of visual flow of the app before building the whole thing as it is a low cost/effort way to visualise the concept and agree on the user journeys and UI/UX. Many times clients provide us with their own wireframes. If there are none, we create mock-ups using our design system.

Step 5 — Project Management

We use ClickUp for setting up and onboarding for each client. Clients can access all onboarding material and tasks for their project.

Step 6 — Database Architecture

Once we have the front-end sorted with a list of user-stories and some screens, then it's time to switch to the database architecture. This is the foundation of an application. We use a number of helpful tools to map DB architecture depending on complexity.

Step 7 — Revise Project Timeline Estimate

At this point, we understand the complexity and scope a lot better so we can provide a more accurate estimate of the time it's going to take for project completion.

Step 8 — Regular Check-ins + Async Communication

We have weekly syncs with client and dev team. It usually lasts 30 minutes where we talk about what we did in the previous week, any questions, and what we are going to work on next. Throughout the project, we exchange a lot of emails and Loom recordings for async communication.

Step 9 — Testing and QA

Once a sprint is complete, clients are given access to marker.io, a feedback tool which makes it easy to report any bugs. Once a bug is reported, a task is automatically created in ClickUp and assigned to the developer.

We hope this was useful. If you have any questions, please contact us.