Can we package a web site as an app?

Assuming this is an information website, stuffing all the HTML and JavaScript bits into the bundle and rendering the website contents from there is certainly possible, as is running an app-embedded web browser and rendering the remote website within the app, but it’s all closer to a “why bother?” app implementation.

The link you’ve cited is centrally about downloading apps and executing code and app content loaded from a remote website, and that’s probably not going to pass app review.

Closer to what you’re trying, what does your proposed wrapped-website-app do that Safari access doesn’t? Or as Apple puts it, see section 4.2 of the App Store Review Guidelines - Apple Developer.

Providing a link to the website would be the easiest, and that link can be saved on the iPhone or iPad home screen, or to the Mac desktop. Here’s how to do that:

…or contact Developer Support, and get the official answer directly from Apple.

ps: for what you’re trying to do—and which probably won’t pass app review as an app, but can work as a Safari access—see the following example (I’ve not tried this, but it seems close to what your website owner wants, sans installed app):

… https://www.freecodecamp.org/news/how-to-turn-your-website-into-a-mobile-app-with-7-lines-of-json-631c9c9895f5/

No one can tell you ahead of time if your app will be approved or not. Even Apple isn't going to tell you that.

All you can do is consult the App Review Guidelines and make sure that you are confident that Apple will approve your app.

What you have described so far suggests that your app will not be approved. Apple isn't in business to help your business. Apple is in business to sell iPhones. That's it. That's the business.

How does your app meet Apple's needs? If Apple feels that the availability of your app will give the iPhone additional value, then they will likely approve it. Any comparisons to Android are pointless. Apple owns the best customers. They would be more than happy to use your app's exclusive availability on Android as a selling feature for the iPhone. That may sound brutal, but it's a brutal world.

No one here can be certain of what Apple might or might not approve, but an app that solely wraps a website isn't going to be highly viewed by the app reviewers, per what's in the previously-cited app store review guidelines.

Side-loading apps isn't typical on iPhone or iPad, and is not something that most users of Apple platforms would do or would even experience. Android users can get in trouble with side-loading sketchy apps, too.

It is possible to have low-volume distribution of apps from the app store, but that doesn't fit here, and—again—it is unclear what Apple might approve here, and this app looks like a whole lot of work at risk of not getting approved, and of not adding anything past what the website itself can offer the vendor and the vendor's customers.

A QR code can bring the user directly to the website, and the website can then provide specials, sign-ups, online ordering, and the rest. With the permission of the users, notifications of specials or whatnot via push, or via email.

Were I the store owner, I'd want to spend more time with the website and what's possible there—which is generic, and its contents and displays and behaviors are also more directly under my control—than with apps for the various platforms.

Beyond a traditional adaptive website design... Maybe... Maybe... Websites and webapps? It's quite possible to download anything from a rudimentary to sophisticated webapp from a website, though that's a somewhat larger investment than traditional straight HTTPS and JavaScript website design. But what's possible here is in the same range as an app for Apple or Android. For example, the entire Linux operating system, BSD, and a number of other Intel x86-64 operating systems can be booted entirely within a web browser, and some: more info. (And to be absolutely clear, I don't expect the store owner would ever remotely want or need bootable Linux in a web browser, this example is provided solely for you and for others reading here to better understand the scale of what's possible within a modern web browser, without dealing with an app store. Oh, and most of us would prefer not to download Linux over a mobile data plan.)

MrYossu wrote:

"How does your app meet Apple's needs?"

Maybe look at it in the other direction. You have an e-commerce site, right? Suppose I wanted to sell my app on your site. What criteria would you use to decide whether or not to feature my app on your site? Would your focus be on on my needs or your needs? Why would Apple be any different?

Sorry, I'm a software developer, and not an Apple user at all, and was naïve enough to think that they would be interested in people producing apps, as that would offer the users more choice. Seems I was wrong!

Apple has over 23 million registered developers and over 2 million apps in the store. Apple doesn't lack for either. Unless you plan to bring a really top-quality user experience to your app, then I wouldn't recommend attempting it.

MrYossu wrote:

Thanks to both of you. As I said, I'm a software dev, not the site owner. I can't see why he's so obsessed with an app, but given that he is, I said I'd ask. As far as I'm concerned, the idea is a waste of time.

Not so fast. Just as Apple has its own interests, so does everyone else. You are a software developer, not the site owner, right? What is in your best interests? What could you do with some Apple app development experience? You should be up-front with the owner about the risks, costs, and strategies for success. But you should also be aware of the opportunities it presents. It isn't your job to decide what is best for the company. It is your job to implement solutions for the company and to decide what is best for you, your family, and career.

It is possible to build this app. It just can't be a re-packaged web site. Rather than fault Apple for this policy, look at how the policy can help both you and the site owner. What features could you bring to the app to get people to download it, and to get Apple to approve it? What would that take? How long would it take? What would it cost? Would you need to hire people, and be their manager, for example? What opportunities would this present? Could you sell a re-branded version of the app to other sites, perhaps?

I'm not saying don't bother. I'm saying you should be honest about the risks, costs, but also the also opportunities. A re-packaged web site is a non-starter. But if you go beyond that, it might work out. Let the owner decide. If they want to pay for it and pay you to do it, maybe you will be able to do more than re-package web sites in the future.