Whats the best way to deal with master/detail and categories where each category needs a different detail scene

Question

Cuthahotha OP

Created Oct ’16

Replies 1

Boosts 0

Views 2.4k

Participants 2

Ok, wow, what a long title.

Again, new to IOS, and could use some design guidence.

I have a tab based app for asset managment. One tab will deal with utilization of the assets, track hours, etc. The other tab is used to enter the assets and configure the various properties.

Assets can be broken down into different categories. Should be between 10 and 15 total categories in the end. Each category has a specific set of parameters I need to track. There's probably a 50% over lap in the parameters between the various categories, eg, make/model/mfg/date purchased. And there's probably 3-4 parameters that will be generated by the system. Hourly usage, number of usages, last maintenance, attached assets (related items)

My thought is to provide the users with a grid of images representing each category. User clicks the category, and they go to a master/detail controller set. This means up to about 15 master/details with specific detail views.

Does this make sense for an approach? Is there a way to keep one master/detail controller, but go to different details. I guess I could have one detail screen and make elements visible based on which category, but that seems like it could be a night mare later.

Any advice greatly appreciated.

Thanks,

Steve

Boost

Answer 1

KMT OP

Oct ’16

Accepted Answer

>could use some design guidance.

In that case, be sure to dig into the iOS HIGs / https://developer.apple.com/ios/human-interface-guidelines/~ Design Principles

About those 15 master/details - Apple generally recommends flattening your UI as much as possible, so sure, one master, many details would be good - again, see the HIGs.

And since you mentioned image grid, a different approach from SVC might be a Collection View (grid/line oriented flow):

https://developer.apple.com/library/content/documentation/WindowsViews/Conceptual/CollectionViewPGforIOS/Introduction/Introduction.html

And since you mentioned tabs, see: UIKit User Interface Catalog: Tab Bar -keeping in mind that while a SVC should normally be the root controller, it can be used with a TBC as root.

Splitview / Master Detail docs are here: UISplitViewController

And finally, if you do go with SVC, be sure to start with Xcode's templated project.

Good luck.

Ken

0