How would I go about making a simple iOS app that simply has to display "data sheets" (just text documents basically) in a way reminiscent of OS X's Finder's Column View?
I want the interface to present a list of Manufacturers. I select one and then a bunch of Models made by that Manufacturer come up. I select one and finally I'm presented with Years. I select a Year and then I am shown a list of all variants of that Model made in that Year. When I press one of these Models I'm shown a textual data sheet for that model.
I mean, I don't even know whether to start this as a Master-Detail Application (although that sort of looks like it might work), a Page-Based Application, a Single View Application or a Tabbed Application...
Thanks
Essentially, you will nee dto get in to UITableView.
It's fairly simple:
https://developer.apple.com/library/prerelease/ios/referencelibrary/GettingStarted/DevelopiOSAppsSwift/Lesson7.html
https://www.weheartswift.com/how-to-make-a-simple-table-view-with-ios-8-and-swift/
Be sure to work 100% using storyboard, and Swift. In answer to your final question simpy start it as a single view app.
Interestingly, once you get good one of the toughest and most expert-level skills in iOS is dynamic height cells in table views. Example of that.
Related
I'm looking for a tutorial (video or written) explaining how to create the iOS contacts app and especially the "add" modal view.
So far I made my way through to believe that the iOS contacts app would be made using static table view cells but I'm not sure if that's a) right and b) still state of the art as almost all Youtube tutorials regarding static table view cells are more than 2 or 3 years old. Is there anything I'm missing?
Disclaimer: I'm learning to code using Xcode and Swift for a few months now, having taken 3 online courses but all sample apps are rather basic apps without much design and functionality or not in that way that I'd need them for my app idea (add and edit via modal view). Please bear with me as I think as a newbie I just don't know the right search expression to find these on say Youtube.
Thanks alot!
Welcome to Stackoverflow.
So far I made my way through to believe that the iOS contacts app
would be made using static table view cells but I'm not sure if that's
a) right
Static tableView is literally for static data. I checked the add modal screen of iOS contacts app, and the data there are very dynamic. So you won't be able to use static tableView for that.
So proceed with the dynamic tableView. However it would definitely require quite a lot of work if you would jump into that quite advanced UX. Another approach for adding a data, in an easier way, is to push a new screen for adding new contact, and then pop it when done. If you really want the iOS contacts app's UX, you may search on tableView begin/end updates.
and b) still state of the art as almost all Youtube tutorials
regarding static table view cells are more than 2 or 3 years old. Is
there anything I'm missing?
Someitmes there's no problem with old tutorials. They can still help. But be aware of deprecated stuff they are trying to teach.
If you are new in swift and xcode, so i recommend to learn swift5 and SwiftUI.
we are using storyBoards but in SwiftUI every things had change.
It is new and it will grow so fast.
https://www.udemy.com/course/ios-13-app-development-bootcamp/
this is not about contact app, but you can use this toturial for your goal
I have a screen with 1 button. When clicking that button, a list of items should be shown (in which the user can select multiple items).
On android, i would like to do this using a dialog. I create a "DialogService" that does this, no problem.
On iOS, however, it seems that the best practice is to display a fullscreen tableview, for example as a modalView. Is it possible to do this without using a custom viewpresenter (e.g. modalViewPresenter)? I would very much prefer to have identical navigation on both platforms and just have different implementations of "DialogService"
I think trying to make one platform look and act like another is generally not a great idea as things start to look weird for the users.
But if you want to do it anyway I would start by trying to do something like this https://stackoverflow.com/a/29910246/1107580 (it is in objective-c) then trying to bind to the tableview that is in the alertcontroller.
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.
I'm looking to create a grid of icons from which one can be selected (see the Daytum app for an example of this).
Are there any existing form entry frameworks for iOS that already support this (eg QuickDialog is excellent, but doesn't support this)
What would be the best way to implement this? Assuming selecting an icon brings the user back to a form field with the icon populated in the field.
Are there any other apps apart from Daytum that use this 'model?
Three20 has a grid view controller, that makes it pretty easy to add icons in a grid.
I'm a huge fan of AQGridView. Used it in a couple of projects and i think its really really built well and easy to implement.
I am new to Iphone programming. So please don't mind if I ask some basic questions. :mad:
I want to develop an application where the landing screen will be a login screen and after login application should display a new screen with the list of available categories. And on selecting any category a new screen should appear with the information related to the selected category.
Basically I want to display different screens in the applications and my confusion is how can I make different screens with one .xib file? or should I use different .xib files for each screen. If I use different .xib files for each screen then how should I navigate to different screens.
Please help in solving this confusion.
Thanks in advance
Gaurav
You should definitely use different .xib's for each view. You will end up having a standard view, a table view (probably programatically wrapped in a navigation controller) and a standard view, respectively. Each will also have their own class.
You navigate to different screens by programmatically initializing them. The condition on which they are created varies from screen to screen. For example, your login screen will only create and load a table view for the categories after a successful login. The category screen will only create a detail screen when the user touches a category in the table.
I think your best bet is to pick up an iPhone programming book and do the first few chapters until you feel comfortable with the basics of XCode. The Apple documentation usually contains more than you really need to know and by the sounds of it, you just want to jump in and make a few simple apps.
After that, you can look at the Apple sample code here: http://developer.apple.com/iphone/library/navigation/index.html#section=Resource%20Types&topic=Sample%20Code