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?
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 7 years ago.
Improve this question
im making a Lib for online payment, which will be plugged in merchant's apps, in my Lib have a popup view with Textfield which letting the user to input their PIN code in it
As i think the merchant can write something to get the inputted key in their app in background when my view is show, so i would like to know if thats possible and how to prevent something like that?
Prevent something like capturing keyboard event without needing of textfield delegate like in click here or click here
Thanks
You can make it difficult for the hosting app, but you will never be able to make it impossible to read the PIN. To make it difficult, you will need to create your own PIN entry with its own "keyboard" possibly similar to the PIN entry for the iOS lock screen.
I would avoid using a keyboard, as users can insert their own keyboard, and thus wouldn't use any of the standard text entry fields. It shouldn't be too hard to create a matrix of 11 buttons (0-9 and a backspace) and the code to display it.
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 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
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.
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.