Apple 4.3 guideline - What to do

Dear,


We saw that many topics here are relared to that, but we could not find any reasonable solution, that's why there's another case of study.


We publish magazines from very different publishers. Each magazine has their own content, trademark, subscribers... each publisher hires us to publish their content inside an individual and most of times custom apps. We don't work with apps generator, we develop in native language all the source code and we compile each app.


As they all are magazines, they are very similar and have the same concept. I mean, magazines are magazines everywhere, we can't change their format... all magazines will have a download option, next, previous, forward, backward buttons, subscriber and buying system... there's no great news about it.


However, Apple rejected some apps saying that it doesn't follow the 4.2/4.3 guidelines and recommended that we put all apps inside a container. Well, i don't need to say that it's not possible...


What to do?


Apple is doing that against small companies only? I mean, the TIME publisher has all apps very close to each other.. each TIME magazine has it's own app and they are equal. Why TIME can update their apps and we can't?


Time magazines = https://itunes.apple.com/us/developer/time-inc/id321041853?mt=8


Thanks

>and we compile each app.


As a consultant, and each mag has it's own dev account, right?


>there's no great news about it.


Sounds like the definition of app spam - without showcasing the platform and making the app perform beyond what can be done via other channels, it needs the store more than the store needs it.


>we can't change their format...


Rather than using that as an excuse to only do the minimum, imagine your success if you did leverage changes... Consider that instead of holding you back, Apple is pushing you forward by providing the opportunity to be and do more.


As for TIME - it should be no surprise that that is a class system involved.

Maybe the guideline will change some day (or maybe not).


Until then, what is best for your clients?

If they'd like to be able to have their apps on the store, then the simplest path to success is probably to act as the app's owner and publish with their own account.

Thanks guys.


Maybe the solution is suggesting customers to create their own accounts... really bad but that's ok.

This solution was solved? Because its seens like same issue. My customers creates their own accounts, but the 4.3 Spam will take it out again, because already exist another app with the same estruture or not?



Thinking about it, 2 or 3 customers upload their apps so its give a rejected spam because its the same app each other, dont you?



sorry for my bad english

Creating owned accounts does not fix this issue, confirmed with our company.

So this guideline is more serious than I thought. How can I develop unique feature app for each customers with low budget? Container app in some case is not an option. This would greatly limit the amount of apps that an individual developer could create.

Yes it's all open ended, and Apple didn't think this through. They should be concentrating on apps where the developer is the client and creating copy cat apps for itself to make money or game the system. However, if the app is created for an outside customer, that app should be fine, especially if they want it under a seperate account.


An example I saw on here is a developer that creates a hunting app for different type of animals, a gorilla, tigers, bear, each with their own app. This right here should be one app, and you pick which animal within that app you want to hunt. Having 30 different apps, for 30 different animals is ridiculous.


However, if I have a totally different organization who wants an app, then this should be acceptable as it has nothing to do with other organizations the developer might of done in the past. These should not be grouped into one app since we are dealing with different customers the developer is working with, especially if they are under a seperate account.


Apple has this wrong, and is enforcing it wrong. They should have a REAL appeal process where they can distinguish these two scenarios.

They are literally not reading responses. Don't bother. Here's a transcript:



Aug 27, 2017 From Apple

Guideline 4.2.6 - Design - Minimum Functionality...
Guideline 4.3 - Design...

Next Steps...


Aug 29, 2017 From Me

I submitted an appeal but received no confirmation e-mail. Did it go through? Do I need to resubmit my app or just wait now?


Aug 30, 2017 From Apple

Guideline 4.3 - Design

We ask that you consolidate your existing apps...


Aug 30, 2017 From Me

All I am asking is if my appeal was received? There was no e-mail confirmation.


Aug 31, 2017
From Apple

4. 3 Design: Spam

Thank you for your response. However we still find that the previously addressed issue still persists in your application...

We have the same issue - we even created the container app that they have requested for this type of content and resubmitted. The response came back identical, "Please consider using a container app"! The reply came within abot 10 secs of the app going into review, so I can't believe anyone even looked at my reply. Are these being generated by a bot somewhere?


I spoke to Apple Developer support and they agreed it was odd. Appreantly there is nothing they can do.

We redesigned our app to make it more customizeable and much more reliable and flexible together with iOS 11 compatibility. We had the exact same experience. App In Review for 10secs then Rejected. I wonder what is heppening in Apple HQ

I doubt AppStore abuse of rights, the audit team we just rejected the first time, have been added 10 days delay of audit, being an iOS developer I feel the shame, I hope you can be sold by the new iPhone is very good, but I believe that more and more freedom will not like apple, because you like a dictator!!!!!!

Apple 4.3 guideline - What to do
 
 
Q