Skip to main content

Twitter like App rejected [closed]



I have an App which is rejected which behaves as the Twitter App on the ground that:







10.4 Apps that create alternate desktop/home screen environments or simulate multi-app widget experiences will be rejected







with as description:







We found your app includes a dashboard view which presents multiple windows at once, and is therefore not in compliance with the App Store Review Guidelines.





The iOS Human Interface Guidelines allow for multiple screens in an app but access to these screens should always be sequential, never simultaneous.





Please see the attached screenshot/s for more information.





It would be appropriate to modify your app by determining an alternate way users can accomplish the same task in a single screen or a sequence of screens.







The screenshot attached is seen below. Can anybody explain what exactly the reason is, looking at the Twitter App. Anybody with a similar experience and a possible solution apart from completely dashing the current interface and putting the ordinary split view controller in?





enter image description here


Comments

  1. While I applaud your implementation, it wont make Apple approve you any faster or even at all.

    The reason they are rejecting, as they say, is because you can interact with all of those views at once. Standard navigation would push one view over the top of the last using the navigationController and sliding effect. Because Apple views this as a widget type effect where everything is all still running at the same time, you are getting the boot.

    One suggestion might be to take a look at how Path and Facebook are implementing the navigation controllers with the slide out effect. You could probably implement something similar where you can just slide the old and the new views on screen. You still need to completely obscure the other views I think to pacify Apple for this rejection. Sorry their ruling wasn't more favorable. Good luck with your appeal and/or corrections.

    ReplyDelete
  2. They also say going to the press upon rejection doesn't help your appeal. Just FYI. I went through one appeals process and said "My app is just like X" and they said (literally), "Thanks for your feedback, unfortunately...."

    I'd keep your appeals to yourself (not trying to be mean).

    Last piece of advice is to make sure there are no detectable errors or incomplete parts of your app. The more polished it is going in the better.

    ReplyDelete

Post a Comment

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex