Presenting a login with storyboards for iOS - ios

I have a simple iOS Master-Detail Application
-> On the iPad it's a splitview, on the iPhone it's a simply a tableview with navigation
Now I need to have a login first but I just can't find a proper solution for it.
I think the only part of the application that should decide whether a login needs to be presented is the AppDelegate.
But how would I have to wire my storyboard to be able to do that on both.. iPhone and iPad?
The other idea is to start with the login and dismiss it if it's not needed any more. But I also can't push or modal present a splitview on the iPad...
How would you solve this problem?
Without storyboards it's easy.. but with storyboards for me it seems hard do to... but I have to admit that I don't have any storyboards experience so far...
Thanks for helping

http://maybelost.com/2011/12/tutorial-storyboard-app-with-core-data/
Download this sample app. It contains a Login with CoreData. Its very simple :)
Several weeks ago i used that also for my first Login and it worked like charm.
Hope it will help you too!

Related

UISplitViewController with best behavior

Until now, I used UISplitViewController with static UITableView and segues.
here a little exemple of my storyboard
(I have multiple DetailViewControllers)
But not working like I want.
I want UISplitViewController like iOS Settings app & Notes app, that is to say, I don't want re-load my UIViewController when I selected it (like Notes app). And if I selected the actually UIViewController embedded in a UINavigationController, I want automatically get a "popToRootViewController" totally like iOS Settings app.
I've done a lot of research and couldn't really figure out how to set this up.
I'm French and not very good in English so please excuse me if I'm not very clear.
Thank you.

Side menu on UISplitViewController like Gmail iPad App

How to put a side menu bar on the UISplitViewController like Gmail iPad App?
Based on Apple Documentation on UISplitViewController, it always must be the root of the application. I have tried to put the UISplitViewController into a navigation controller and it doesn't work
https://developer.apple.com/documentation/uikit/uisplitviewcontroller
Can anybody guide me on how to achieve such layout? I am totally lost. Been figuring it out for days and still can't find any solution.
If there is any library out there that can help me to achieve this function, will also be so appreciated.
I am using Swift 4. Thanks in advance!

Segue back button disappeared in iOS 9

Before iOS 9 was released, I've developed an app targeting iOS 8.4. I've used some UITableView connected each other via segue of kind "Show (e.g. Push)". It worked perfectly with the right behavior: every time I switched from a UITableView to another, the back button appeared, so the user is able to turn back to the previous scene; the back button appeared also from UITableView to UIViewController, using the same kind of segue. Now I have upgraded to the latest version of Xcode and targeting the app to iOS 9.0, I got this problem: now, if I go from UITableView to another UITableView, the back button doesn't appear anymore, but if I go from UITableView to UIViewController, the back button appears. I've seen other developers has had a similar problem (as you can see here, here and here), but I don't understand how they have solved (except for the third link, but it's not my case). Anyone knows how can I get back button working again? Thanks in advance
It looks like the guy who posted the second link is having the same problem as you. In a comment he said that the way he fixed it was getting rid of the extra navigation controllers:
No need put the navigation controller for each view. put the navigation controller start view only.
So that is what I would suggest doing. Only put a navigation controller on the first view controller. Get rid of all the others.
So, thanks to Caleb's and ogres' suggestions, I solved my problem in this way as you can see in this screenshot, I hope it helps anyone who will have the same problem!
If you have two UITableViews and you want connect them to each other, you just need one NavigationController.

App starting as Single view and proceed to tabbar application

I am about to create an xcode iphone app which will lauch initially as a single view ( something like login and settings screens ) and then proceed to a tabbed bar application with multiple tabs .
how to do this -
should i create two differnet projects one single view and one tabbed application ?
and is it possible to roll two projects into one single app ?
or is there just another easier way. I have xcode 4.3 and planning to use storyboard insteaod of XIBs
rgds,
sumit
Do not start with two projects, as you'll have an incredibly difficult time integrating them into one app. This is pretty simple, but you do need to learn the basics of view controllers.
Use Storyboards, and start with a single view app, maybe inside a navigation controller. Then do a transition to a tabbed view controller.
Upgrade to Xcode 4.6.3 or 5. Look at Apple's template apps for a tabbed application and a single view app to see how the storyboards look. Then copy the storyboards in one to the other, and link them up. This is definitely possible and straightforward, but you do need to understand how each view controller works with the others.
I also faced same situation once. I made a project as single view based app. without storyboard (since I was required to build compatible apps with iOS 4.3).
Made login screen as main view controller.
On login, I presented tab viewcontroller modally.
On sign out, I dismiss tab controller and return back to login screen.
If you have any queries, just ask it :)

Multiple SplitViewControllers in iPad Application

We are creating an iPad application that uses multiple SplitViewController. From the Apple documentation I understand that the SplitViewController needs to be the rootViewController of the window.
Does anyone have any experience or suggestions on how to create a navigation scheme that switches between multiple SplitViewControllers?
Its seems that this is not a supported design. We have since decided to use one SplitViewController at the root, and swap out it's views when the screen changes. This seems to work pretty well.

Resources