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.
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 9 years ago.
Improve this question
The camera app on iOS allows one to take a photo, but also has the button to the left that allows one to browse the photo album.
When using the UIImagePickerController I can only tell them to either do one or the other.
So, rather than making a custom camera view, or even a custom overlay to add these abilities, I'll ask if there isn't some sort of flag I'm missing to allow this use case.
When invoking it, you choose which one you want. There isn't a way to get exactly the same functionality as the camera app unless you, as you said, make a custom view for it. But wherever you want to invoke this, you could provide the options for either choosing a photo or taking one at that point.
You'll notice other apps that either let you take a photo or choose one from your library give you those as separate options within their UI.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
Basically, as the title of the question says: I would like to know how important it is to have an edit button when all I want the user to be able to do to a cell is delete and 'swipe to delete' is enabled. Is it intuitive enough if the edit button is not there? Are iOS users all very familiar with 'swipe to delete'??
I would rather not have the edit button there if I'm able to delete by swiping, but how would a user know?
It is personal preference. I believe the swipe to delete is more of a super-user feature and people new to iOS may not find it, if you see the Apple Message app, both are supported, you can swipe to delete or press edit then delete.
However, see the Apple Notes app, and swipe to delete is the only way to delete a note without actually going in to it.
Analyse your target user base and make a decision, or try observing some people using the feature. Is there a reason why you can't have an edit button? Is something else in the nav bar?
As CodeBox says, this is more of a user-experience discussion than a right/wrong programming question.
https://ux.stackexchange.com/
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 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.