Guideline 4.2 - Design - Minimum Functionality

Question

ahomag OP

Created 18h

Replies 1

Boosts 0

Participants 2

Hello everyone, My app has been rejected for the 10th time for the same reason.

My app was a web app running in WebView.

They sent me a screenshot of my app's left menu, saying it didn't have enough content and rejected it. With Giude 4.2,

Then we asked why, but we didn't get an answer. They just copied and pasted the 4.2 clauses and sent it. We didn't understand, and I think we made the app native because it was a website, but some pages are still displayed in WebView.

The main screen is native, the left menu, and even the user menu. However, 2-3 screens inside open WebView.

I've developed the same app 23 times before this for different companies. Now a new client wants it, but I can't.

Two reasons are mentioned in the forum:

If the app can be used as a website, create a website, not an app.
If it's displayed entirely in WebView, don't do this. Make it native.

I have to create an app. I'll send notifications and use the camera. I promised my client I would develop an app for him. So, I need to eliminate item 1. But it's out of my hands.

As for item 2, can't there be a webview on just one or two pages? I'm not sure if I should make everything native.

Can anyone help?

Thanks.

Boost

Answer 1

darkpaw OP

10h

My app was a web app running in WebView.

Don't do this. No one wants to have to download an app when they could just as easily go to a website and perform exactly the same actions there. That's why your app was rejected.

If the Review Team sent you a screenshot of the 'left menu' saying it didn't have enough content, then you should add more content to the app.

2-3 screens inside open WebView

Write those pages as native pages inside your app rather than merely views onto a web page. Make the experience native, i.e. the user is in an app on iOS, so make the experience look and feel like they're in an app in iOS, rather than them having downloaded an app and being sent to a website.

I promised my client I would develop an app for him.

You seem to be coming at this from the wrong direction. You promised your client you would develop an app for them, but you're trying your hardest to simply shoehorn a website into an app 'shell'. That's not a good experience for the users, and it's not what your client wants. Approach the problem from the angle of creating an app with the features that the client needs. Build each screen as required. What you're doing seems to be merely adding a web view that goes to an existing web page. Not good.

0