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
If I'm making an iPad app for a questionnaire that consists of 10 "yes/no" questions, what is the best way to go about this from a UI design pattern perspective?
I want only 1 question to be shown at a time. I have thought about maybe a UIPageControl, but that doesn't seem to really fit. Also I have thought about a self looping segue on the question view controller, but this also seems like it might have its own problems. What about a sidebar with each question in a list?
What is the standard/accepted/best way to go about this type of problem from a UI perspective?
With this requirements, my solution is to use a navigation controller with 1 ViewController that takes 3 params: question index, question content (to be displayed), response (to be chosen). Application begin with first question then go next for another question. The answers will be saved into a Dictionary.
If one question is shown at a time with yes/no, I'd use UIAlertView control personally. This way you can use many different dialogs, Here is Apple Developers Reference on UIAlertView:
https://developer.apple.com/library/ios/documentation/uikit/reference/UIAlertView_Class/UIAlertView/UIAlertView.html
If you have multiple selections or multiple choice questions use UIActionSheet. See my SO answer:
Creating UIActionSheet
I had the exact same problem 1 year ago and I used a self-looping UIViewControllers (I'm not a huge fan of storyboard). I didn't see any problem with that. With proper data structures set up, you can very easily allow user to answer/go back/exit.
Related
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 5 years ago.
Improve this question
I am looking for either the terminology or a reference on how to do this.
When you Successfully build a project on Xcode a nice, looking alert pops up. Like the one below:
I have found only one other question on how to recreate this for Mac OS. I want the iOS version. I want to use this alert to show a count down for a timer. I have the count down fully functional but I'm not sure of a good way to display. I think this would be ideal for it.
I have the count down fully functional but I'm not sure of a good way to display
It's simply a view (UIView), with a transparent grey background color, rounded corners, and a light shadow. All of that can be readily be configured by straightforward view and layer properties in about three lines of code, and showing the view can be as simple as one line of code.
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 6 years ago.
Improve this question
I'm working on a quiz app.
The thing I've noticed is that my questions may not always have a fixed number of answers. Instead of say, 4 possible answers and 1 correct answer, I could have 6 possible answers with 2 correct answers.
Is there a way to deal with this?
What I don't want to do is have buttons not in use.
At the moment I'm wondering if there is a way of having multiple view controllers depending on how many possible answers there are, or to have the buttons become inactive if there is no answer to be selected?
It is fully possible. You should use a TableView / CollectionView to achieve that.
You will be able to change the number of items, according to your answers count, and allow user to select from 0 to N answers.
Moreover, it it is reusable components, so you will have to design your UI for 1 question, and all the following will reuse the same layout
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 9 years ago.
Improve this question
I'm implementing a settings screen in my app that has several sections.
Section-wise:
May be something like general app settings like:
only download over WiFi
disable auto dimming
May be something for a different category of settings lik:
default text size
etc.
So... In total I'll have 4 or 5 of these sections and each will contain 2 - 5 options.
Some of the sections will have headers and others may not.
I've attached a screenshot of the Vesper app to show the idea I'm talking about.
My question is this:
Is it best to use a UITableView with Sections (grouped) to accomplish this, or just separate UIViews manually placed at the positions I want them?
(For what it's worth, I'm not using Interface Builder)
In the end, UITableViews only take care of presenting and reusing UITableViewCells, which inherit from UIView, so your question is basically "should I reinvent the functionality the table view already provides?"
And the answer is no, you shouldn't.
Even though you won't be getting much out of the "reuse" mechanic of table views, you will still be able to use everything else, the ability to hide/show rows animatedly, maybe some of the cells are identical (like text weight cells) and can be reused from the same identified queue, etc.
And if you want to implement a settings outside the app, then take a look at the settings bundle, you don't even need to code, you just link a few plists together and get an interface done for you.
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 9 years ago.
Improve this question
For example, if you do it all programmatically, are you less likely to run into trouble?
if you are designing UI with code (not using Xib/Stotyboard) this will be good when you create UI dynamically so then you need not to spend more time on changes. what ever we use for development (Code/Xib/Storyboard) nothing will be changed in performance. As per user/developer comfort we will go for it. Suppose there are lot of UI need to be displayed few at the time viewdidload and rest after some button action then usually at the initially stage itself Xib and Story board will load all of them and hides un wanted and as per actions it will show the hidden UI. i feel coding is better for me.
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 2 years ago.
Improve this question
I want to put a feedback form in a view in my IOS application.
There will be 2-3 smiley images. Initially they will be in grey color. When you tap one of them, it will be colored, and the rest stays grey. They will work like radio buttons in HTML.
And there will be 5 questions.
So, what is the best way to handle this feedback form in a native IOS application?
Thank you.
In my opinion the best and most simple way would be to do it with an embedded html page. This is great if you already have such a page for the web version.
Another way would be a custom made form in a xib, with custom buttons, but in order for you to actually receive that feedback, you would need to somehow send the data trough a scripted page (php, asp or whatever you like).
I've done similar things and I used the second suggestion I gave you but in my case it was different, because that form had to be presented over an existent view with animation and so on. What I would recommend you is the first one, with the web page.
I think you can use the xib to create the view with the question text and buttons for answer options. The buttons can have the smiley images as background image.
Then you can change the image for the smiley on button click for the button state selected. and may be have another button to confirm answer and move to next question that is refresh view with new question text.
Hope this helps.