I have a need for two UISplitViewController in my app and i am switching back and forth between them using rootViewController swap. Are there any risks in getting the app approved ?
thanks
All rules that are used during app review are described in App Store Review Guidelines.
Point 10. User interface has such rules:
10.1 Apps must comply with all terms and conditions explained in the Apple iOS Human Interface Guidelines.
10.3 Apps that do not use system provided items, such as buttons and icons, correctly and as described in the Apple iOS Human Interface Guidelines may be rejected.
iOS Human Interface Guidelines have such rules for Split View Controllers:
Avoid creating a secondary pane that is narrower than the primary pane.
Avoid displaying a navigation bar in both panes at the same time.
In general, indicate the current selection in the primary pane in a persistent way.
Give people alternative ways to access the primary pane, if appropriate.
As you see it says nothing about switching between different objects of UISplitViewController. You will be good as you are not trying to display both split controllers at the same time.
Related
I have a blurred view which overlays other views.
UIVisualEffectView is not appropriate because it is disabled when user sets Accessibility >> Reduce transparency.
Could you suggest how to show this blur always independently from the device settings? Both UIVisualEffectView and custom control are applicable. And both swift and objC solutions are applicable
You can prevent Acessibility from applying to a view by using:
self.accessibilityElementsHidden = YES;
This being said, you shouldn't go against Human Interface Guidelines. There is a good reason why accessibility features exist.
Human Interface Guidelines - Accessibility
Here are some excerpts from Apple's App Store Review Guidelines to explain.
10.1 Apps must comply with all terms and conditions explained in the Apple iOS Human Interface Guidelines
10.3 Apps that do not use system provided items, such as buttons and icons, correctly and as described in the Apple iOS Human Interface Guidelines may be rejected
I am developing an app in which i am putting tab bar on top as per requirements.I know apple put tab bar at bottom with maximum 5 tabs.So if make my own custom tab bar & i put it on top.
I have two questions.
Will apple human interface guidelines will be violated?
If i violate apple human interface guidelines will apple reject the
app on app store?
Short answer:
1. Yes, that's not the appearance on tab bars on iOS
2. No
Long answer:
As long as you're designing the tab bar (that's what you call it) to be easy to use and it's clear to understand its purpose, then no harm is made. If, however, there is no clear purpose, why move it?
Apple will not reject apps that violates the HIG, but the HIG is created to be followed, to create a consistent experience for all users, regarding app.
I want to design a page with tab bar on top of it.In some articles of this site.(i missed urls) i found that this is not a common way and the question gets some down rate.
The question is this: whethere having a design like this may cause that apple not approve the application on his store?
Even if it doesn't make Apple reject your app, think of the users not being used to the tab bar being at the top and how that is going to affect how well the app does in the Store.
Every platform has its own design patterns and there is a reason for that. If you stick to them there is a higher chance that the first-time users have an easier time using your app, which results in a higher chance that they keep using it. If they don't know how to use it or find it hard, they will move to another one.
Take a look at the Human Interface Guidelines and apply them. It will do good.
Closed. This question needs debugging details. It is not currently accepting answers.
Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.
Closed 3 years ago.
Improve this question
I'm currently developing an app for a client which makes use of a tabbar, but I'm concerned I may be violating the human interface guidelines.
My app starts with a home viewcontroller which leads to several other viewcontrollers. One of the viewcontrollers has a tabbar. The very first item on the tab bar is a home button. Clicking the button will send the user back to the home viewcontroller. The home view controller does not have a tabbar.
The question of the hour ... is this a violation of the human interface guidelines?
I know the suggested route would be to use a navigation controller and my client may certainly agree to it, but I'm concerned if the current configuration is doable.
Thanks for your advice
Firstly I would say that it violates the HIG in that this is unexpected behaviour to iOS users. In the HIG it states that you should embrace IOS UI Paradigms, which means that you should not mimic built-in apps, but follow the design patterns of those apps. What you are trying to achieve is something that the user does not expect (as this is not normal behaviour) and therefore is not really the right way to go.
It also might violate the HIG in:
In general, use a tab bar to organize information at the application level. A tab bar is well suited for use in the main app view because it's a good way to flatten your information hierarchy and provide access to several peer information categories or modes at one time.
Your application puts a tab bar inside the app and not at the application level. But as the text says, you should generally adhere to this.
However I do not think it is particularly good UI to do this, as it is confusing to the user. At one moment there is a tab bar and then when pressing a tab the tab bar is gone. I would definitely rethink the UI problem you have and use another mechanism for it (like UINavigationController) or try to use the tab bar differently by using it at the application level.
I have developed an app that has work successfully for the last 4 months using iOS 4.3 and under. Since iOS 5 however the tightening of view hierarchy has left my app dead in the water. The app starts with a tab bar as its main view with 5 tabs. When the user selects a row on a tableview on the first tab it pushes onto another tabbar with 3 tabs which gives specific information about that selection. This structure worked fine but obviously broke when testing on iOS 5.
My question is: Is it bad design to utilize 2 or more tab bars in one application? I don't mean "bad design" in the grand scheme of things because that is subjective. I mean in a practical sense where it is specifically forbidden or not recommended.
have a look at this:
iOs Human Interface Guideline
Yes, I think that it's not recommended.
For example:
Use a tab bar to give users access to different perspectives on the same set of data or different subtasks related to the overall function of your app. When you use a tab bar, follow these guidelines:
Don’t use a tab bar to give users controls that act on elements in the current mode or screen. If you need to provide controls for your users, use a toolbar instead (for usage guidelines, see “Toolbar”).
In general, use a tab bar to organize information at the application level. A tab bar is well-suited for use in the main app view because it’s a good way to flatten your information hierarchy and provide access to several peer information categories or modes at one time.