Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 4 years ago.
Improve this question
Which is the tool used to design UI View Controllers and storyboard for iOS NIB UI?
[UPDATE]
I'm looking for a UI Design Tool in terms of layout sketches more than the StoryBoard design of XCode. The aim is to design the flows of the UIViewControllers as depicted by Apple in the iOS Developer Library.
I have checked some layout UML Class diagrams tools like Visual Paradigm, Magic Draw, etc, but they do not have a visual layout for the UI as well.
UIStoryBoard is the great way to start its easy and fast way to create UI for all ios application
You can start with studying basic template code - e.g. tabbar application for your purpose - File -> New -> Project -> Tabbed application.
Navigation: To navigate from one screen to other screen - you need to embed in navigation controller - Editor -> Embed In -> Navigation Controller/Tab bar Controller
Connection: Ctrl + drag to another view controller to push from one scene to other scene..
Navigation can be done via code see Navigate storyboard via code
Here is an good tutorial for learning storyboards Tutorial on Storyboard
You can build all of this very easily in storyboard. Just create a new project and click on "use storyboard". You them drag onto the storyboard the first view and click on "editor" then "embed in tab bar controller". Then click on "embed in navigation controller". To connect views one to another you hold ctrl and drag from one view to another. This is a fabulous tutorial: http://www.raywenderlich.com/50308/storyboards-tutorial-in-ios-7-part-1
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 1 year ago.
Improve this question
So I'm currently evaluating using the UISplitViewController, but had accidentally been trying out the iOS 14's version. Aside from the 3 column's displays, I also noticed in XCode there's an option in the Storyboard called Use Separate View Controller for Compact Width's.
I tried this out and it does seem to work pretty flawlessly. However it doesn't appear to be an option in the iOS 13's UISplitViewController.
Is this something can be done through code? I just find it a little jarring with the iOS 13's one when you display it on an iPhone, it shows the Detail page with the back option.
Our iPhone App's main layout is a UITabViewController, we are exploring the UISplitViewController for the iPad version and wanted to make use of it as the main full size iPad's display and then have it be able to fall back to our UITabViewController when it's in a compact width state.
if we want to set it in code behind , we just need to set the style like following
MasterViewController controller = new MasterViewController();
this.SetViewController(controller, UISplitViewControllerColumn.Compact);
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 3 years ago.
Improve this question
I am new iOS development, I used storyboard and Interface builder to design my application UI. But now I am seeing that many people are using SwiftUI. I searched about SwiftUI and found some points about it as SwiftUI works seamlessly with new Xcode design tools to keep our code and design perfectly in sync. But I am not able to compare it with Interface builder & Storyboard. What are the advantages & disadvantages of SwiftUI over Interface Builder and storyboards?
Is SwiftUI will completely remove Interface Builder and storyboards?
In the interface builder like storyboard and xib you can see what you are doing. You take a component and then add it to the storyboard and that's how you design the UI, but if you do the same thing programmatically then it gets a lot harder as you can not see anything and you have to be experienced to do so. Every time you have to build an app to see the changes in the UI but SwiftUI solves this issue as it gets updated constantly as you write code. To solve this, Apple came up with SwiftUI which helps you to see what is going side by side. Anyone can move from Storyboard to SwiftUI.
Personally, I have started from Storyboard then moved to XIB and then I went to Flutter which was quite different and SwiftUI is quite inspired by Flutter. You have to keep in mind that SwiftUI support starts from iOS 13. You have to start from storyboard and then when you have gained experience then you can move to SwiftUI.
Update: Also, there is an another way of developing UI's and that is via programmatic UI coding. I have been developing UI's programatically for a long time now and personally it helps to understand the concepts of UI more and you can start adding a lot of extensions which will make your project easy to maintain at a later stage. When you develop in a group then interface builders throw merge conflicts a lot of time which becomes a pain very soon. (30 Oct, 2020)
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 6 years ago.
Improve this question
I would like to start with an excerpt from Segue Types: "In iOS, the segues are further divided into segues that adapt to size classes and the older, now deprecated types."
So, adaptive for segues means the same thing as it does for layouts: we can specify a set of segues wherein the segue that is actually used is determined by the size classes that are in effect (the same as we do when we create a set of size class dependent auto layout constraints). Great! However, as far as I have been able to discover, there is no way to actually do that. Can anyone help to clarify this?
New segues adapt to presentation style, not so much to the size classes (although the two go hand-in-hand).
The idea is to help you build a storyboard that targets both iPhones and iPads, with their different styles of presenting data hierarchies arranged as master-detail.
Building a universal application with old-style segues required your app to see if you are in a split view controller (bigger screen) or in a navigation controller (smaller screen), sending a Push or Replace segue based on a situation. New segues let you send a Show or a Show Detail segue, which sense the view controller kind, and do the right thing for your UI style.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 7 years ago.
Improve this question
I've an application and in that I need a side bar just like navigation drawer in android. I've seen several third parties but it seems they are not useful for me. Because I've more than 5 ViewControllers and in each ViewController I need the same Sidebar. How can I do it. And i'm a beginner please help.
try these MMDrawerController its very easy to understand and implement,it offers lots of customization..
https://github.com/mutualmobile/MMDrawerController
There are several libraries that help you accomplish this; a simple Google search for "ios navigation drawer library" will give you some examples. However, please note that this is considered poor UI design these days.
However, if you still want to accomplish this, and you are worried about sharing amongst view controllers, you could use a top-level UINavigationController to hold your child view controllers. Or you could make your own container view controller where you swap out the child view controllers but still show the navigation drawer button somewhere.
There are a Good number of Third Parties available at cocoacontrols.com and at github.com.
goto cocoacontrols.com and type navigation menu or drawer on search bar you will find a lot of answers. Demos are also given in github.
Example links:
https://github.com/mutualmobile/MMDrawerController
https://github.com/aryaxt/iOS-Slide-Menu
https://github.com/JVillella/JVFloatingDrawer
https://github.com/dogo/AKSideMenu
download the zip file and include it in your project and follow the instructions.
But somehow Third party is third party. If you wanna avoid third parties, try popover menus for the same purpose.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I have list of mail items in one View and I have nav bar button "New" to create new message.
All samples I've seen online say that this "new message" screen should be modal. We open it, write message and send it. Thats it. Since there is no navigation from this screen - it's use case typical modal view.
But I find that I really like "Push" this view. I get title for free, I get back button for free, I can add "Send" button to preconfigured title bar.
In code I can do "pop" on navigations stack after entered message processed. What's bad about it? So, it sounds like it should be modal but "push" much easier to do via storyboard.
According to Apple's Human Interface Guidelines:
Use a modal view when you need to offer the ability to accomplish a
self-contained task related to your app’s primary function. A modal
view is especially appropriate for a multistep subtask that requires
UI elements that don’t belong in the main app UI all the time.
Modal Views
This is largely a preference thing and depends upon what you are trying to accomplish and whether you care if the user explicitly acknowledges his edits or not (i.e. save/cancel). It sounds like you have a reasonable case for push in your example so I would go with that. If you find that you are moving toward implementing features of a modal VC while using a push, then switch over to modal. I do not believe there is a hard and fast rule for this.
The following answer provides some additional nice reasons to go modal or push
Modal vs. Push