The Airdev process is built to deliver powerful, production-grade applications for companies of every size. Our team of no-code experts scopes, designs, and builds your product, in a fraction of time and cost of traditional developers.
This initial step is meant to help decide if we’re a good fit for your project. This includes assessing tech feasibility, your team’s goals, budget, and timeline, and aligning expectations so that we can together decide whether to proceed.
You begin by booking a call with an Airdev account executive to discuss your project and our approach. They will understand your team, what you are trying to do, and the most critical product requirements to get there. From this call they will write out a summary for our product team, which will review and confirm technical feasibility and budget/timeline alignment.
The result of this step is a high-level written proposal for the build: the features we would build, expected budget, and stages/timeline to get to launch. While the exact details will be confirmed during the formal scoping process, our aim at this step is to give you the information you need to have confidence that this is the right path for you. When you’re ready, you’ll put down a refundable deposit to reserve time with your PM for scoping.
The goal of the scoping step is to align on the exact features and architecture for your app. Taking the time to define everything upfront helps us to move quickly during the build, and ensures that you get what you are expecting.
We start by matching you with a Product Manager (PM) from our team who we believe will best serve your needs. During your calls with the PM, you’ll walk through the entire app flow, stopping at critical points to decide what to include vs. push for later, and the best ways to solve for the requirements within budget. We typically anchor on the leanest approach, and let you push to add features as needed. Our team will perform technical research and document all requirements.
The result of this step is a detailed scope document that outlines the exact users, pages, and features your initial product will include, as well as a timeline and budget for the build. By this point you will have clarity on how your vision translates into a specific product.
With feature requirements in place, the final step to the pre-build process is to add high fidelity mockups that define what users will see as they interact with your product. This is where the UX designer comes in.
Using the written feature descriptions from the scoping doc, the UX designer creates a full set of custom Figma mockups for your app, using our Canvas design framework with your company's branding. This means you’ll get designs that are (1) custom to your features, (2) follow best practices and standard UX conventions, and (3) fit our build process so they can be assembled efficiently.
Once all pictures and words are combined, you have the entire scope doc that will serve as the blueprint for your build. You can submit any detailed feedback within this doc, and your PM can make adjustments as needed (including corresponding budget/timeline updates) until you are comfortable with the plan.
Some clients prefer to use their own custom designs, which can add a significant amount to build cost and timeline, so large majority of our clients opt for Canvas and consider a redesign post-launch.
With the detailed build plan in hand, the focus shifts to your Airdev build team, which builds and tests the complete application in weekly milestones.
Your PM will manage a team consisting of a lead developer, UI assembler, and QA specialist. Each week, the team builds and tests the features we have designated for that milestone, and delivers the working app along with testing instructions so you can confirm everything is working as expected. Your PM will hold a live delivery call with you to make sure we’re aligned and ready to proceed with the following milestone.
This stage ends when a full version of your app — with all features internally tested by Airdev — is ready for your final review before launch!
Even the most basic software products have complexity under the hood, and can take some time to fully test and confirm. For every build, we provide a 30-day window of coverage from our team to confirm, launch, and support the application.
When we turn the app over to you, our internal team has finished our QA process, so the first step is for you to thoroughly review every aspect of the tool and flag anything that is not built according to the confirmed scope. We have a nifty widget so you can mark up the app itself to create tickets, which we clarify and resolve.
When you're ready to go live, we deploy your app on your custom domain and transfer all credentials and IP rights you. Celebrations and AirHugs for everyone! Any remaining time in the 30-day window is extra support just in case you spot anything that slipped through the cracks.
As you approach the end of your “review and launch” period, your Client Success manager will contact you to chat about what comes next. For most clients, launch is just the beginning since app generally must evolve in response to user feedback.
We offer two forms of post-launch support: (1) one-time capacity to build discrete features, and (2) ongoing monthly capacity to maintain and build features over time from the roadmap. The former is typically best for early-stage clients on a budget, and the latter is best for more mature clients with a robust roadmap and need for constant support.
Overall, we recognize that your journey and needs can be unpredictable. Our goal is to give you control of when and how you use your Airdev team to get there.
Great software requires a team of specialists minding every detail of the build process. Each Airdev project comes with...
A dedicated Product Manager (supported by a Senior PM), to help define your exact feature requirements
An expert UX Designer, to create custom high-fidelity Figma mockups for your build
A Bubble UI Assembler, to assemble your pixel-perfect responsive front-end design
An expert Bubble Developer, to optimize your app's database and logic for performance and scalability
A QA Specialist, to perform end-to-end testing on your app
A Client Success Manager, to support you each step as you maintain and scale your product
Our in-house project portal (built on Bubble) guides the project team through each step of the build, ensuring that expectations are aligned and deadlines are met. Clients can track timelines, discuss open tickets, manage invoices, and more – our aim is peace of mind through an orderly and transparent process.
Executing a build requires a wide range of expertise to design, assemble, and test every feature. With a 3% acceptance rate and a global workforce of 100+ no-code professionals, we staff each project with specialized talent that plugs in at the right points to deliver exceptional quality.
Each project team can leverage a wide range of centralized resources, including Canvas building modules, technical assets, building playbooks, and on-call product/technical/design experts. These tools prevent wasted effort and bottlenecks, resulting in a faster and more reliable process.
Learn about our freelance program through which you can hire individual expert developers
FROM OUR BLOG
No-code has made it possible to build in just weeks. But product development timelines can vary depending on whether you want to build your app for efficiency or speed. Here's a quick guide to determining how long your app will take to build according to your needs and goals.
When building an app without code, it can be hard to know which features to include/exclude in your first version. Here, we'll provide lessons we’ve learned that can help guide your feature selection.
Will I be able to scale my app built on Bubble?
Yes. We always design apps to optimize for scale, based on our understanding of the potential features and user behavior our client envisions. The Bubble technology is built to scale, with the ability to upgrade server capacity as needed (including migrating to a dedicated AWS cluster) to service a growing user base. Bubble provides simple dashboards and notifications to track app capacity usage to help you adjust as needed.
Will my Bubble application be secure?
Yes. Bubble is built on Amazon Web Services (AWS), which is itself compliant with certifications such as SOC 2, CSA, ISO 27001, and more. All data behind Bubble apps is stored in the cloud using AWS and is generally hosted on AWS West Region (Oregon, US) which maintains a state-of-the-art security infrastructure. Below are more of Bubble’s security features:
How much will my no-code app cost to build?
We price our projects based on how much effort they are going to take. The key factors are how much functionality you're looking to build, how complex the functionality is, and whether you we use our design framework or implement a custom design. Feel free to reach out if you'd like to get a quote for your project, or read more about Airdev’s approach to pricing here.
Who owns the IP rights to my application?
You own the rights to your concept, your application, and all user-generated data created through the app. Airdev retains the ownership of the IP for our predesigned page and element templates that we use across multiple projects. More details on this distinction can be found in the client contract you can review before approving a build.
Is Airdev able to support and extend my application as it grows?
Yes, you can come back to us at any point after the initial build for additional work. You can request ad-hoc updates or sign up for a monthly plan, which will come with a certain amount of team capacity.
What technology will my application be built on?
We build on the latest visual programming framework, Bubble, which allows us to build incredibly quickly and flexibly with minimal technical input. This reduces the cost and headache to our clients, and increases app stability out of the gate. Bubble itself is written in CoffeeScript running on Node.js, uses Postgres databases hosted on AWS, and exposes POST or GET APIs for third-party connections. The app can be easily connected to external APIs and the app's database can be easily exported. Learn more about Bubble here.
What are the limitations? What can you not build?
There are a few categories of tools that we can't help with:
- Fully native mobile apps (e.g. Whatsapp or Uber) - though web-based mobile apps are supported
- Existing products written in code
- Apps that need to work without an internet connection
If you're not sure whether we can do what you need, we would be happy to help you find out!