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 colorful wireframe built in Figma or XD. Sometimes it's an existing application that we need to remake or take over. Sometimes it's an amazingly large spreadsheet, which is somewhat like an application 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

Understandably, the first step after signing a new project is to prepare as much as possible ahead of kick-off and make the rest of the journey with us smooth for our clients.

We share a checklist of the type of access we need. We have a large list of questions that we need to ask about the app. This is where we fully understand your expectations, collect all your requirements and identify any roadblocks that we might come across.

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

The principles of agile in software engineering apply to NoCode as well. We occasionally come across features or plugins we haven't used before. We need to test these areas first to completely de-risk the app. Questions like, can bubble 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 visualize the concept of the app and agree on the user journeys and UI/UX. Many times clients provide us with their own low-fidelity wireframes. Sometimes there's an existing app. If there are none, then we use Airdev’s Canvas kit to create mock-ups.

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 on Clickup

Step 6- Database Architecture

It gets a bit more serious now. 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 (DB) architecture.

DB architecture is the foundation of an application. We use a number of helpful tools to map DB architecture depending on complexity of the app including spreadsheets, DB diagrams and IO.

Step 7- Revise Project Timeline Estimate

At this point, we understand the complexity and scope of the app a lot better so we can provide a more accurate estimate of the time it's going to take for project completion. We are now fully equipped to build the app in Bubble.

Step 8a- Regular Check-ins

We have weekly syncs with client, Zubair and dev team working on the project. It usually lasts 30 minutes where we talk about what we did in the previous week, any questions that we have and what we are going to work in the following week.

Step 8b- Async Communication

Throughout the duration of the project, we exchange a lot of emails and loom recordings. Because our clients and development team is spread across the globe, this enables prompt communication.

We have a number of integrations in place. Our Team@AZKY email is connected to Clickup. So the feedback shared by clients is automatically recorded in the thread.

Step 9- Testing and QA

Once a sprint is complete, the clients are given access to marker.io, a handy feedback tool which makes it super easy to report any bugs or mistakes in the app,. Once a bug is reported, a task is automatically created in Clickup and assigned to the developer to action on.

‍

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