Hannah is the operations director for a group of eight veterinary clinics across Ohio. After a lengthy board meeting and a longer lunch, the owners had agreed that the clinics required an app. Owners of the animals wanted to be able to make appointments, view vaccine schedules and receive reminders for refills without having to wait on hold. But there was no consensus as to its construction. One partner was looking for a no-code tool as his nephew had created a restaurant menu that way. Another said that they were “the real thing” and insisted upon native apps. Instead, a third has wanted to find a Mobile App Development company which could simply take care of the whole thing and end the conversation.
The hardest part of the budget was none of it, according to Hannah. It was that each and every alternative seemed to make sense until she entered into a comparison. Not the same question and not the same answers.
That’s a standard problem and here’s how she solved it and a blueprint that any business can follow when deciding on how to create an app.
There Are Really Three Decisions, Not One
Most people treat “how should we build this” as a single choice. In practice, it is at least three, and mixing them up is where projects go wrong.
The first is the technology approach: native, cross-platform, progressive web app, or no-code. The second is who builds it: an in-house team, a freelancer, or an agency. The third is how you work together: fixed price or time-and-materials, large release or small ones. Hannah separated these on a whiteboard and found the board’s arguments suddenly made more sense. Her partners had been debating different layers without knowing it.
The Technology Options, Plainly Explained
Native development involves creating different applications for iPhone and Android, with the use of Swift for iOS and Kotlin for Android. Native Apps provide the highest levels of performance and have the most access to the device features including health sensors, high level camera controls and the most recent capabilities of the platform. They also imply two code bases, two sets of skills or teams and often more time and money.
Both apps are developed with a single source code that can run on any platform. The most popular frameworks are Flutter and React Native. Almost the same UI experience as a native application and quicker and more cost-effective to build, most business apps are indistinguishable, for booking, ordering, messaging, account management, etc.
PWAs are applications that run within a browser but act like applications with an icon on a home screen and some offline functionality. They’re simple to deploy and update, but they don’t have access to all the device features, and on iPhone they have more restrictions than on Android.
No and low code platforms such as Bubble, Glide, and FlutterFlow enable non-developers to create apps graphically. These can be a great method for rapidly testing an idea. The compromises are revealed later when the customization is limited, the performance is capped, the platform is locked in and it is hard to integrate with the older platform.
Start With the Users, Not the Technology
Before they picked out anything, Hannah’s team did something simple. They canvassed at the front desks of approximately three hundred pet owners and found out which phone they are using and what features they would like to see in an app. It was a nearly even 60% iPhone, 40% Android split, making it impossible to develop for one platform alone.
They also provided what the app required. The main functionality consisted of booking, reminders, and secure messaging. Uploading of photos for the skin condition was an added bonus. Of course, there were no advanced sensors or heavy animation, which meant that native’s considerable advantages did not come into play. But that was just a sign that she was headed in the right direction towards cross-platform.
The lesson is this: it should be driven by your users and feature list. Native is more appealing if your app needs augmented reality, Bluetooth devices or intensive graphics. When it’s primarily used to move data from a person to a database, cross-platform is typically sufficient.
Integrations Often Decide the Outcome
Many projects get more form and direction from what the app needs to be connected to, than from the app itself. Hannah’s clinics were based on a practice management system which was used to record appointments and patient records. She had to communicate with it in some way if she was to use either of these.
The system had a small interface, and a no code tool was not able to maintain that connection. A custom backend could. This was a move that got her away from the no-code booking system the partner had selected, but not that she used it to prototype and get an idea of what the booking process would look like before investing.
Get feedback on systems early on as to what you need to connect to and how well documented they are. If a feature appears simple on a slide, a thin interface can make it twice as hard to work with.
What Each Approach Costs
“A number” is a priority for owners at all times, and here is the truthful answer. The approximate range of Mobile App Development Cost for a typical business app is reasonable to compare within the scope of the project, integrations, team location, etc. The range of a no code prototype is from a few thousand to about thirty thousand dollars. The range of a custom app that is cross-platform is typically between sixty thousand and one hundred eighty thousand. Typically, the price of natively built apps is pretty competitive, ranging from one hundred twenty thousand to three hundred fifty thousand dollars. It’s usually about fifteen to twenty percent of the build per year, as Apple and Google release new OS versions which require support.
Hannah’s build across platforms sat at almost $112,000. She added about $6,000 for a two week discovery period at the beginning, which she says uncovered three requirements the board didn’t think to consider.
In-House, Freelancer, or Agency
The second decision is who does the work. An in-house team gives you control and long-term knowledge, but it takes time to hire, costs a lot in salaries, and only makes sense when software is central to the business. Freelancers are flexible and often affordable, though continuity can be a risk if one person leaves. Agencies offer a full team of designers, developers, testers, and project managers, at a higher hourly rate but with more reliability.
Hannah didn’t have the volume of work to justify hiring engineers, so she chose an agency. She checked references from two similar businesses, asked who would own the code, and requested a written explanation of what would happen if the relationship ended. Those questions told her more than the portfolio did.
How You Work Together Matters
Fixed-price contracts feel safe because the number is clear, but they often punish change. If you learn something halfway through the project, which you will, a fixed scope makes adjusting expensive and awkward. Time-and-materials contracts offer flexibility but can drift without discipline.
Many teams land on a hybrid. A fixed-price discovery phase, followed by a series of short build cycles with regular demos. Hannah’s team shipped something she could tap through every two weeks, which meant problems surfaced early rather than at the end.
Test Before You Commit
Whatever approach you choose, put something in front of real users early. Hannah ran a four-week beta with about sixty clients through TestFlight and an Android test track. The testing exposed two issues the team hadn’t expected: some pet owners wanted to manage several animals under one account, and the reminder texts were arriving from an unfamiliar number. Both were fixed before launch.
What Changed
Eight months after the original board meeting, the app launched across all clinics. Online booking now accounts for roughly forty percent of appointments. Reception staff field fewer routine calls, and refill requests arrive in a tidy queue rather than on sticky notes.
Hannah says the real win was the process. By separating the decisions and asking what her customers needed first, she found an approach that suited her business instead of the one that sounded most impressive.
That is the broader point for any company. There is no universally right way to build an app. There is only the approach that fits your users, your systems, your budget, and your tolerance for risk, and the best way to find it is to ask the dull questions first.





