App Development Services 2027 for Small Business
app, web app or just a better websiteHi there, friend. My app development services start with an awkward question: does your business need an app at all? Sometimes it does. Often a fast mobile website or a progressive web app does the same job for less. I take on app development projects, and I scope each one with you on WhatsApp before anyone spends a cent.
- scoped before quoted
- honest “you don’t need an app”
- store listing included
- You describe the idea. What the app should do, and who would open it.
- I ask who, how often, and why. The answers decide between an app, a web app and a website.
- You get a plain recommendation. If it’s a project for me, a written scope follows. If it isn’t, I say so.
Regulars reorder the same cakes and ask about opening hours
| route | fits when | effort |
|---|---|---|
| Better mobile website | orders, menu, hours, found on Google | low |
| PWA (web app) | repeat orders, home-screen icon, some offline use | medium |
| Native app | deep phone features, store presence matters | high |
// example decision, not a client project. The highlighted row is the recommended first step here; the effort column is a rough relative guide, not a quote.
Website, Web App or Native App?
Many projects that ask for an app are better served by a fast website or a web app. Pick the tab that matches your goal.
Best when you need to be found in Google and your users arrive from search.
Best for logged-in tools. It can still be installable and works on every device.
Best when you need deep device features such as push messages or the camera, and users will install it.
// a general guide, not a rule. Send me the idea and I will say which one I would build.
What an App Looks Like in Code
I write apps for the web and for phones. Here is the same small task, showing a greeting, in three languages.
@Composable
fun Greeting(name: String) {
Text(text = "Hello, $name")
}
struct Greeting: View {
let name: String
var body: some View { Text("Hello, " + name) }
}
const greet = (name: string): string => `Hello, ${name}`;
document.body.textContent = greet('world');
// tiny examples to show the languages. A real app also needs design, data and testing.
Do You Need an App, or Is a Website Enough?
You need an app when the same people will use it again and again, and it needs something a web page handles badly. If customers visit once or twice a year, a good mobile website wins, because nobody installs an app for a single visit.
A Good Mobile Website
People find you, read, call or book, and leave. A locksmith in Phoenix needs a fast page with a phone button, not an icon on a stranger's home screen.
A Progressive Web App
Regulars come back often and want it quick, maybe offline. A bakery in Leeds taking pre-orders from the same customers every week is a typical case.
A Store App
Daily or weekly use, plus deep use of the phone itself or a need to be in the app stores. For example, a gym in Toronto with class bookings, check-in and reminders.
| question | if yes | if no | weight |
|---|---|---|---|
| Will the same person open it every week? | app or PWA | website | high |
| Must it work with no signal? | app or PWA | website is fine | mid |
| Does it need deep phone features? | store app | PWA may do | mid |
| Do customers expect to find you in a store? | store app | PWA or website | low |
| "Our competitor has one" | not a reason | not a reason | none |
// my own rule of thumb, an opinion and not an industry standard. The example businesses are made up.
What a Progressive Web App Is, in Plain Words
A progressive web app, or PWA, is a website that can behave like an installed app. MDN, Mozilla's developer reference, defines it as an app built with web technologies that gives a user experience like a platform-specific app.
In practice that means two things at once. Like a website, it runs on many devices from a single codebase, which is one set of code. Like an app, it can be installed on the device, work offline and in the background, and plug into the device. Google's web.dev sums the goal up in three words: capable, reliable, installable.
The entry ticket is small. According to MDN, a web app needs a manifest to be installable. That's a short file with the app's name, icons and start page. It must also be served over HTTPS, the encrypted connection behind the browser padlock. A service worker, a script that keeps the app usable without a connection, is common but not required for installing.
However, there are limits. Install support differs by browser: MDN notes that on iOS 16.4 and later people install from the Share menu, and that Firefox on desktop doesn't install PWAs from a manifest. web.dev also admits some capabilities are still out of the web's reach. So I check your must-have features against real devices before recommending this route.
a_pwa_gives_you
- One codebase for every device
- An icon on the home screen
- Offline use, if built for it
- Pages Google can crawl like any site
a_pwa_does_not
- Reach every phone feature
- Install the same way everywhere
- Appear in a store automatically
Corner Bakery Orders
a 192px and a 512px icon
the page that opens first
standalone: its own window, no browser bar
required, or the browser won't offer install
optional for install, needed for offline
// requirements as listed by MDN for Chromium-based browsers, checked 11 Nov 2026. The bakery name is an example.
Native vs Cross-Platform vs Web App, Explained Simply
A native app is written separately for each phone system, a cross-platform app is written once and packaged for both, and a web app runs in the browser. The right one depends on your features, your users and your budget for upkeep.
| Native app | Cross-platform app | Web app or PWA | |
|---|---|---|---|
| What it is | Built for one system: one app for iPhone, another for Android | One shared codebase, packaged as an app for both systems | A website that works like an app in the browser |
| Codebases to maintain | Two, if you want both systems | Mostly one | One |
| Where people get it | App Store and Google Play | App Store and Google Play | A link or a search result; installing is optional |
| Phone features | The fullest access | Most of them, sometimes with extra work | A growing set, with gaps |
| Store review before release | Yes | Yes | No, unless you also package it for a store |
| Store account fees | Apple $99 a year, Google Play US$25 once | The same two fees | None for the web version |
| Found through Google Search | Through your website, not the app itself | Through your website, not the app itself | Yes, its pages are web pages |
// a general comparison in my own words, not a ranking. Store fees are vendor-stated (Apple Developer Program; Google Play Console Help), checked 11 Nov 2026. The highlighted column is the cheapest route to test an idea, in my opinion, and not the best route for every project.
You'll notice I haven't named a favorite toolkit. That's on purpose. The route gets chosen in the scoping chat, from your feature list, and I tell you plainly whether your project is one I take on.
How I Do the Scoping
I turn your idea into a short list of features for version one, and I push everything else to "later". Scoping means deciding exactly what the app will and won't do before any design or code exists.
This is where most of the money is saved. Every extra screen has to be designed, built, tested on several phones, and maintained for years. So first I ask what a customer must be able to do on day one. For a hair salon in Sydney that might be: see free slots, book, get a reminder. A chat feature, a points system and a photo gallery can wait until real people use the first three.
what_i_do
- Ask who uses it and how often
- List every feature you imagine
- Sort into must, later and cut
- Recommend app, PWA or website
what_you_get
- A written scope for version one
- A screen list in plain words
- A quote based on that scope
| feature | who needs it | decision | version |
|---|---|---|---|
| see free time slots | every customer | must | 1 |
| book and cancel | every customer | must | 1 |
| reminder the day before | every customer | must | 1 |
| loyalty points | regulars | later | 2 |
| in-app chat | almost nobody | cut | none |
// example data. Green rows get built; the crossed-out feature costs more than it returns.
How I Do the Design and Build
I design the screens as simple sketches first, get your yes, and only then build, one working piece at a time.
First come wireframes, which are plain box drawings of each screen with no colors. They show what sits where and what happens when you tap. Then comes the visual design, and then the build in small steps, so you can try real screens on your own phone early.
Most apps also need a back end. That's the part you never see: the server and database that store accounts, bookings or orders. If your website already holds that data, the app should talk to it and not keep a second copy. Because I build websites too, I plan both sides together. See my web development services for that half.
what_i_do
- Sketch every screen and tap
- Design after the flow is approved
- Build in small, testable pieces
- Connect it to your site or data
what_you_get
- Screens to approve before code
- Test builds on your own phone
- Honest progress, including delays
// example flow for a booking app. Five taps is the idea; every extra step loses people (my opinion, not measured data).
How I Do Testing and Store Submission
I test on real phones, fix what breaks, and submit only when the app is finished, because both stores check apps before they go public. A rejected submission costs days, so the checklist comes first.
Apple's App Store Review Guidelines are specific. Submissions should be final versions with all metadata and working links, and placeholder text should be gone. Every app must link to its privacy policy, both in the store listing and inside the app. And an app should offer more than a repackaged website. So if your "app" is your website in a wrapper, Apple may say no, and they'd have a point.
Both stores also need a developer account. Apple's Developer Program is listed at $99 a year, and Google Play charges a one-time US$25 registration fee (both vendor-stated, checked 11 Nov 2026). I set these up in your name, so the app belongs to your business and not to me.
what_i_do
- Test on small, large and older phones
- Test slow and missing connections
- Prepare the privacy policy link
- Submit and answer the reviewers
what_you_get
- A test sheet you can read
- Store accounts in your name
- An app that passed review, or the reason it didn't
| check | why | status |
|---|---|---|
| no placeholder text | Apple guideline 2.1 | pass |
| all links work | Apple guideline 2.1 | pass |
| more than a website | Apple guideline 4.2 | pass |
| privacy policy linked | Apple guideline 5.1.1 | pass |
| no crash on old phone | basic quality | fix first |
// example sheet. Guideline numbers refer to Apple's App Store Review Guidelines, checked 11 Nov 2026. Passing review is never guaranteed; the reviewers decide.
How I Do App Store Optimization
I write your store listing so the right people find the app and understand it in seconds. App store optimization, or ASO, is SEO for the store's own search box, and the rules come from Apple and Google themselves.
Apple says its search results depend on text relevance, meaning matches with your app's title, subtitle, keywords and primary category, and on user behavior such as downloads, ratings and reviews. The space is tight: 30 characters for the name, 30 for the subtitle, and 100 for the hidden keyword field. Apple also advises against repeating words from the name in the keywords, and against plurals of words you've already used. Promotional text gets 170 characters and doesn't affect search ranking, so keywords there are wasted.
Google Play has no keyword field. It gives you 30 characters for the app name, 80 for the short description and 4,000 for the full description. Google states that apps are ranked on a combination of ratings, reviews, downloads and other factors, and it warns that repetitive or irrelevant keywords can get an app suspended. So the old trick of stuffing a description with search terms is a fast way to own no app at all.
what_i_do
- Research what people type in the store
- Write name, subtitle and descriptions
- Plan screenshots that explain the app
- Set up a routine for asking for reviews
what_you_get
- A listing within every limit
- The keyword list, with reasons
- No fake reviews, ever
Shear Salon: Book a Haircut (27 characters)
Appointments in Sydney CBD (26 characters)
Apple allows up to 10; the first ones show in search
// limits from Apple's product page guide and Google Play Console Help, checked 11 Nov 2026. Google Play's full description (4,000 characters) is left off the chart for scale. The salon listing is an example.
How I Make Your App and SEO Work Together
I give the app a home on your website and connect the two, because Google Search sends people to web pages, not into app stores. Your site finds new customers. Your app keeps the regulars.
So every app gets a landing page: what it does, screenshots, and the store buttons. That page can rank when someone searches your business name plus "app". It also gives AI assistants something to quote, which is part of my AI search optimization work.
Then come the links between web and app. On Android, App Links create a verified connection between your website and your app, so a tap on one of your web links opens the matching screen in the app directly. Android's developer documentation recommends them for exactly this. A PWA has it easier: its screens are web pages already, so they can be crawled like the rest of your site.
For a local business, the same rules as local SEO apply: one name, one address and one phone number, identical on the site, the store listing and your Google Business Profile.
what_i_do
- Build the app landing page
- Link web pages to app screens
- Match names and details everywhere
- Track installs that start on the site
what_you_get
- One brand in search and in the store
- A site and an app that feed each other
- Numbers you can check yourself
// example of the goal, with a made-up salon: your landing page as the first source. No assistant or search engine can be ordered to show it.
From Idea to Store Listing
An app project runs through seven steps, and you approve each one before the next begins. Nothing gets built that you haven't seen on paper first.
step 1 · free
The WhatsApp Chat
You explain the idea. I ask who will use it and how often, and tell you honestly whether it should be an app at all.
step 2
Scope and Quote
Features sorted into must, later and cut. You get the scope and the quote in writing.
step 3
Sketches and Design
Box drawings of every screen first, then the real look once the flow works.
step 4
Build
Small pieces, each one tried on your own phone as soon as it works.
step 5
Testing
Different phone sizes, an older phone, a slow connection and no connection.
step 6
Store Listing and Submission
Name, descriptions, screenshots, privacy policy link, then the store review.
step 7 · ongoing
After Launch
Bug fixes, updates when the phone systems change, and the landing page and SEO that bring people in.
// the order of work. No dates are shown because the length of each step depends on the scope, and I put my estimate in the quote.
What App Development Costs, and How Long It Takes
I scope every app project on WhatsApp first and quote it afterwards, so there is no price list on this page. An honest number needs a feature list, and you don't have one yet.
How the Quote Works
The first chat is free. After scoping you get a written quote for version one. My hourly rate for small jobs and changes is €25, the same as for my other work.
What Makes an App Bigger
The number of screens, user accounts, payments, offline use, two phone systems where one would do, and connections to other software. Each adds building and testing time.
How Long, Honestly
It depends on the scope, on how fast you give feedback, and on the store review, which I don't control. Your quote includes my estimate. I don't promise a launch date before scoping.
Plan for running costs too: the store accounts mentioned above, hosting for the back end, and updates. Phone systems change every year, and an app that isn't updated slowly stops working well.
// my rate is current, checked 11 Nov 2026. No project prices or delivery dates are published because they would be invented.
Common App Mistakes, and How to Avoid Them
Most failed small business apps fail before a line of code is written, at the idea stage. Here are the mistakes I see most, each with its fix.
The Usual Mistakes
- Building an app for customers who visit twice a year
- Putting every idea into version one
- Wrapping the website and calling it an app
- Launching with no landing page and no listing work
What to Do Instead
- Check how often people would really open it
- Ship three features, then listen
- Give the app something the site can't do
- Prepare the listing and the web page before launch
// my opinion from project work, not a survey.
How to Check the Finished App
You can test the result yourself in an afternoon, with no technical knowledge. If any of these four checks fails, it goes back on my list.
- Hand it to someone new. Give your phone to a friend and ask them to complete the main task without help.
- Switch on airplane mode. See what the app does with no connection. A clear message is fine. A frozen screen isn't.
- Search the store. Type your business name and the main thing the app does, and see whether your listing appears and makes sense.
- Search Google. Type your business name plus "app" and check that your landing page shows up after it's been indexed.
Getting Found: Three Monthly SEO Plans
These are my SEO plans, not prices for app development services. An app is scoped and quoted separately. The plans grow the website that sends people to your app, with on-page, technical, local and off-page link building every month.
Starter
For a small local site that needs steady, careful work.
€475/month
- On-page, technical, local and off-page
- 1 to 2 guest post links a month
- Links from blogs with real traffic
- Monthly plain-English report
Growth
For a business with competitors who already do SEO.
€875/month
- On-page, technical, local and off-page
- 2 to 3 guest post links a month
- Links from blogs with real traffic
- More pages and fixes handled each month
Full Campaign
The most SEO work per month of the three.
€1,275/month
- On-page, technical, local and off-page
- 5 or more guest post links a month
- Links from blogs with real traffic
- The most work per month of the three
Set Your Own Monthly SEO Budget
None of the three fit? Tell me what you can spend on SEO each month and I'll tell you honestly what I can do for it. The slider is for monthly SEO work only, not for building the app.
// the same plans as on my home page, where I work as a cheap SEO expert for small businesses. How the monthly work runs is on the SEO process page.
App Development Questions People Ask Me First
Short answers to what small business owners ask before they pay for app development services.
Does my small business really need an app?
Only if the same customers would use it often and it does something a website handles badly. For one-off or rare visits, a fast mobile website is the better buy. I'll tell you which case you are in during the first WhatsApp chat.
What do your app development services include?
They include scoping, screen sketches and design, the build, testing on real phones, the store listing and submission, and a landing page on your website. I take on app development projects and scope each one on WhatsApp first.
How much does it cost to build an app?
There is no fixed price, because every app is scoped first and quoted afterwards. The cost follows the number of screens and features. My hourly rate for small jobs and changes is €25.
How long does app development take?
It depends on the scope, your feedback speed and the store review, so I give an estimate in the written quote. I don't name a launch date before the features are agreed.
What is a progressive web app?
A progressive web app is a website that can be installed and used like an app. MDN describes it as built with web technologies while giving a user experience like a platform-specific app. It runs from one codebase and can work offline when built for it.
Do I need my own Apple and Google developer accounts?
Yes, and they should be in your business's name. Apple lists its Developer Program at $99 a year, and Google Play charges a one-time US$25 registration fee (vendor-stated, checked 11 Nov 2026). I help you set both up.
Can you guarantee the app stores will approve my app?
No. Apple and Google review every app and make the decision themselves. I prepare the submission against their published guidelines, which avoids the common reasons for rejection, and I fix and resubmit if a reviewer asks for changes.
Will an app help my Google rankings?
Not directly. Google Search ranks web pages, so your website still does the work of being found. An app helps indirectly when it has its own landing page and when it keeps customers coming back to your brand.
Tell Me the Idea. I'll Tell You If It Needs an App.
No form, no pitch deck. Send me a few lines on WhatsApp about your business and what the app should do. You'll get an honest answer, even if that answer is "build a better website".
// prefer email? [email protected] works too. Speak soon, friend.
Sources and Last Check
Every limit, fee and platform rule on this page comes from the official pages below.
- MDN: Progressive web apps (definition of a PWA)
- MDN: Making PWAs installable (manifest, HTTPS, service worker, browser support)
- web.dev: What are Progressive Web Apps? (capable, reliable, installable; limits)
- Apple Developer: Creating your product page (name, subtitle, keywords, promotional text, screenshots)
- Apple Developer: Optimizing for App Store search (search factors and keyword advice)
- Apple Developer: App Store Review Guidelines (2.1, 4.2 and 5.1.1)
- Apple Developer Program (annual membership fee)
- Google Play Console Help: Create and set up your app (store listing character limits, keyword warning)
- Google Play Console Help: Get discovered on Google Play search (how apps are ranked)
- Google Play Console Help: Get started with Play Console (registration fee)
- Android Developers: About deep links and App Links (verified links between website and app)
// last checked 11 Nov 2026. My rate is my own. Store fees are vendor-stated. Example data is labelled as example data, and opinions as opinions.