A wrapped app puts your website inside a store-ready shell, which is cheaper and faster but limited. A native app is built for the phone itself, which costs more and earns it only when you need offline use, heavy hardware or speed.
When someone says they want an app, they might mean one of two quite different things. One is your website, packaged so it can be installed from the App Store. The other is software written for the phone itself. They look the same on a home screen and they are very different projects, with different costs, different limits and different risks in review.
Here's how we'd think about choosing.
01What a wrapped app is
A wrapped app is a thin native shell with your website running inside it. The shell is what Apple and Google review and what people download. Most of what the user sees is your site, shown full screen with no browser bar.
One common tool for building the shell is Capacitor, and it's the one behind our own Dry Run app, covered below. The shell can do some things a plain website can't, through add-on pieces called plugins. Push notifications, haptic feedback (the small buzz you feel on a tap) and access to the camera are examples.
It's the quickest route from a working website to the stores, and it reuses everything you've already paid for: the design, the data, the logins. That reuse is most of the cost difference we laid out in what a small business app really costs.
02What it can do
- Be installed from the store. An icon on the home screen, a store listing, a place people can find you by name.
- Send notifications. A wrapped app can send push notifications to the lock screen. The platforms don't charge to send them, which we sourced in that cost post.
- Use some hardware. Camera, haptics and similar features, through plugins.
- Update the site without a store review. Because the content is your website, a change to the site shows up in the app when you publish it, not when Apple signs off. That's a real advantage over native, where every change goes through review. We'd keep it to ordinary content and fixes, though. Apple's guideline 2.5.2 says apps may not download or execute code that introduces or changes the features or functionality of the app, so using the website as a back door to change what the app is would be a risk. If you're unsure where the line is, ask before you rely on it.
03What it can't do well
- Work with no signal. A wrapped site needs a connection unless it's built to store things on the phone, and that's extra work. If the job is a warehouse or a field with no bars, that points to native.
- Feel instant. Heavy animation, big lists and anything that has to respond immediately are better in native code.
- Reach the deepest parts of the phone. Some hardware features are awkward or missing through plugins.
- Pass review on its own. This is the one that surprises people. Apple's guideline 4.2 says an app should go beyond a repackaged website. A wrapper with nothing added is the case it's aimed at. We wrote it up in why Apple rejects small business apps. A wrapped app needs at least one honest reason to be an app, like notifications that matter or a feature that uses the phone.
04What a native app is, and when it earns the extra cost
A native app is written for the phone's own system, so it's built to feel like part of the phone. It can store data on the device, work offline and sync later, use the hardware in depth and respond without a browser underneath it. It takes more time to build and more care to test on both iPhone and Android.
We'd call it worth it when:
- It must work offline. The strongest reason of all.
- Staff live in it. An app a crew opens many times a day is a tool, and the extra polish pays back.
- The hardware is the point. Scanning, tracking a route, a specific camera workflow.
- Speed and feel matter. The app is the product, not a front door to one.
If none of those fit, a wrapped website is usually the better first step. It's a cheaper way to learn whether anybody installs the thing at all. That's the same argument as in do you need an app, or just a website: spend the small amount first and find out.
05Where we'd start for different businesses
A trainer who needs bookings doesn't need either. A site like Ruca Fit's, where clients book a session online, does the job on any phone with nothing to install. A baseball training brand like MADE Baseball, with lessons and camps to show and sell, is the same story. And CageList, the marketplace we run for booking batting cages, is a website on purpose, because an install between a player and a cage would lose bookings.
An app starts to make sense when the customer is in it all the time. That's a rarer situation than most people think. Most of the businesses we talk to need a better website and sometimes a text message system, not a store listing.
06Our own, honestly
Dry Run, our free practice trading app, is the case we're living through. It started as a website at playdryrun.com that you can use in a phone's browser. The iPhone app is a wrapped shell around that site with a few native touches, haptic feedback when you place a practice order, for one. It's built and running on our phone. It's not in the App Store, and store enrollment is in progress.
So we can tell you what the build looks like from the inside, but not what review looks like, because we haven't been through it. We're aware the shell has to earn its place under Guideline 4.2. What happens will be added to these posts, good or bad.
07Quick answers
What is a wrapped app?
A native shell that loads your website, so the site can be installed from the App Store and Google Play. It can add some phone features through plugins.
Can a wrapped app send push notifications?
Yes, through plugins. Neither Apple nor Google charges to send them, though some third-party tools do.
Do I need store review for every website change?
Not for ordinary content and fixes, because the website is the content. Changing what the app does is different, and Apple's guideline 2.5.2 limits code that changes an app's features.
When is native worth it?
When it has to work offline, when staff use it all day, when hardware is central, or when speed is the product.
08Next step
If you're deciding between the two, tell us what the app has to do. We'll say which one we'd build, or whether you're better off with a website first, and the price goes in writing before anything starts. You can also read how we work on the mobile apps page.