Embedding tab bar to top of screen iphone - ios

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.

Related

How are apps with typical menu-bar-style navigation coded?

I’m a relatively new app developer working on a couple of individual projects. I’ve dumped at least one hundred hours into coding using Swift in Xcode, and, as embarrassing as it may be to admit, it seems I can’t fully grasp or find information pertaining to how popular apps such as Facebook, Instagram, YouTube, or Tinder implement non-linear view navigation via a menu bar at the bottom of the screen.
I’ve seen one particular app tutorial series that exemplifies how to go about making this menu bar style possible using a collection view of horizontally-placed views each equivalent to the size of the screen. I understand this gets rid of the issue of loading new views on top of existing old ones that sit in the background (my primary worry, outside of unnecessarily reloading information), but is this the typical method of implementing non-linear menu navigation in an app? I suppose a more pressing question at this point is “How can I go about making something like this using SwiftUI?”
If anyone can offer information, explanations, and/or sources, they would all be much appreciated. Thank you for your time!
So, upon receiving TylerTheCompiler’s comment on my post, I started researching the UITabView. It appears that this is used for creating exactly what I was trying to explain in the initial post. I subsequently searched for a way to implement this in SwiftUI and found the “tabbed view.” The tabbed view seems very easy to implement and is exactly what I’ve been looking for. I still wonder if popular applications have been utilizing the UITabBar rather than something else more practical that I am still unaware of. If you happen to know, please comment on this post — I would love to know, myself. As always, thank you for your time, everyone!

Always on top (on other apps) button in iOS

I am new to iOS development and wondering if it's possible to create a floating button which always stays on top of screen even if you have any other app running in full screen mode?
No you can't do that on iOS, Apple isn't allowing this kind of features (like Messenger on Android for example)
I assume you mean something closer to AssistiveTouch. When turned on in accessibility, it will stay on top of the screen, no matter what app you have open. I recommend reading the Apple Docs for further investigating into this, but at the moment, Apple does not let you do this. Your app can't mess with other apps. It's pretty against what Apple's design guidelines allow you to do.
Is there a work around for what you are trying to accomplish with this? Maybe if you expand your question, I can help.

Can an Apple Watch app have multiple glances?

The question is as simple as:
Can an Apple Watch app have multiple glances?
I tried to put multiple glances in the Xcode storyboard but Xcode said that only one Glance is allowed for each app.
Reason I am asking this is that I would like to change the layout of the Glance based on the information I display.
But the question could also be phrased as:
Is it possible to
change the glance layout programmatically or
load different glances depending on the context.
Is any of the two possible? And if not, is there any indication that this may change after WWDC 2015?
EDIT:
To clarify. I agree, multiple glances seem not to be available, however changing layout of a glance may be (I personally think that they will allow developers to do so soon but as far we are concerned at the moment the only way I can change a glance layout is to choose it from the list provided in XCode).
Currently these are the layouts available for glances (top and bottom part). Ideally I'd like to choose them programmatically. If anyone knows how then please share some code snippet/sample:
Top part:
Bottom part:
An app can have 1 glance associated with it.
However it can be modified from time to time as per your requirement.
awakeWithContext() is called once for the controller. You can do general init work there.
willActivate() will be called everytime the glance controller is about to be initialised and you can request new data, change view there, do other awesome work, etc.
So to answer your question, you can load different glances depending on the context. But an app can have only ONE glance at a time.
Hope this helped.
The answer is as simple as:
No.
I'm not sure about changing it programmatically (haven't tried)
I don't think that you can load different glances.
The point of glances is to allow users to find one piece of info ultra quickly. For that, they need to know what they will be looking at. That's why there is only one glance per app.

iOS design guidelines - tabcontrol versus list view for main/first selection screen

Since Apple developer account is down, I can take the chance of later submiting and getting rejected since I will then run out of time.
Suppose I have 9-11 menu items in main window navigation. It is a bit too much, but that is what customer explicitly requested.
The Android version uses a listview and it works and looks good. It does so on iOS. However, I can see most iOS apps use a tabcontrol at bottom with extra tabs at (...) Is that a strict requirement in all cases? (I can't really say one of the menu items are more important that the other.)
No, using a tab bar controller is not a requirement, that's a design choice. Whether to use a tab bar controller or a list view depends on how you navigate around in your app, and what you want the user experience to be. If you want the user to be able to switch easily and quickly between different modes of the app, or different views of the same data, then probably a tab bar controller would be appropriate. On the other hand, if the choices you're making initially, are not made often, and you have a large number of choices (like you do), then a table view is probably more appropriate.

Risk to be rejected on custom UITabBar

I'm wondering if there's any risk to see the app rejected from the AppStore (iPhone app) if I modify the existing UITabBar making it slightly taller. I'm working on a custom uitabbar with custom background pattern that is also just a little bit taller (8px) than the default one. It additionally has a raised central button.
I really don't see why this could reject the app but I thought I would better ask first since it's quite a lot of work implementing this custom design and I might have overlooked some of the HIG guidelines/rules.
Many thanks,
Tomas
There are tons of apps in the AppStore with custom tab bars, starting with some of the most popular ones like Instagram so you should be safe.
There are huge numbers of apps out there with custom tab bars, including non-standard sized ones and ones with protruding central buttons. They're fine, as long as they work correctly.

Resources