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.
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 2 years ago.
Improve this question
I am need create feature like in iOS "Photos" system app, when you are have a list of photos and use long press to image, this collection view with images exanded, all background is blurred and has appeared popover menu, how I can create it?
I am can detect long press on collection view and add some view behind, also I am try create blur effect but can't blur all behind particular cell.
This is image of this effect effect inside system app
Your screen shot shows a context menu interaction. Since this feature already exists at framework level, and since a collection view is ready to implement it for you, I suggest you just use it rather than trying to reinvent such a complicated thing for yourself.
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 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.
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 6 years ago.
Improve this question
Before I begin, I would like to state that I KNOW the Apple Guidelines state that two popovers "should not" be on screen at one time, and that my app will likely get rejected if it do this, but I wanted opinions as to how this might work. Here is my dilemma:
The iPad doesn't have a numerical-only keyboard (it simply displays the normal keyboard). So I made a numerical keypad control in a popover (for elsewhere in the app) for ease of number entry.
I have a several fields in a popover that only allow numbers in them (by way of refusing any non-numerical keyboard input). Unfortunately, this means that now 90% of the keyboard is unresponsive when entering into these fields - and the numbers aren't even in the front "page" of the keyboard!
However, if I make the fields in the popover popup the numerical keyboard, this user interface confusion is eliminated! But it goes against Apple Guidelines for Popovers! (aside: they call them guidelines, yet they enforce them like hard-and-fast rules, right? :/ )
I'm asking opinions on what I should do here: should I go with one option or the other, or is there a third method I could use?
The correct way to create a custom input layout that appears in place of the normal keyboard is described here: http://www.raywenderlich.com/1063/ipad-for-iphone-developers-101-custom-input-view-tutorial
Also, you can get the iPad to show the numbers on the "front page" of the keyboard by settings the text field's keyboardType to UIKeyboardTypeNumbersAndPunctuation.
Why not just place your numberpad in a seperate view and either animate it in and out or make it moveable/dragable?
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
My UI designer favors a radio style button for Yes/No. I understand there is no such UI component in iOS and I would use two different custom images for normal/highlighted state. However, what I need to know if Apple would allow me to do it. Is there any clause in the human interface guideline against using radio style button instead of SegmentControl style? Help would appreciated, thanks
DONT! This really is something you should avoid under pretty much all circumstances. The Apple GUI team has designed a different control for such task and you should rely on the fact that they really did a great job. Keep in mind that the user is using his finger to use the UI and that a radio-button is more or less designed for a mouse cursor. The "circles" would need to be huge to be properly addressable with a finger. Apple recommends 44points square for any touchable control.
Apart from that, you will not get rejected for creating such custom control.
I think that your designer needs to read the Apple HIG. They should know this is a bad idea.