Can I use Radio buttons in my iPhone app? [closed] - ios

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.

Related

Is a completely custom keyboard, for my app only, acceptable? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 5 years ago.
Improve this question
I'm working on an iOS app that requires a custom keyboard. I'd like some help in knowing if I am allowed to create a custom keyboard for my app only and if I'm allowed to set a custom height on it as well. I've never worked done anything with creating custom keyboards for my app only, and would appreciate if some guidance were to be provided on how to go by starting this if this concept were to be acceptable by Apple. Thank you for your time.
Totally acceptable inside your app! and there should be no acceptance criteria for that!
You can even make a custom keyboard to use outside your app (I developed two myself), however there are acceptance criteria for that (like having a button to switch to another keyboard).
Hope that helps!

Circualr progress bar for Audio [closed]

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 4 years ago.
Improve this question
Now I am developing an app which includes music. On that I am using AVAudio player for playing music. My issue is that I need to show a circular progress bar with Play/Pause buttons. The sample image is attached with this.
How can I achieve this.
you can use components for example
LLACircularProgressView
or
UAProgresssView
and you can get lengh of your audio with :
audioplauer.duration
There are some good suggestions above.
You could also use a UIView, set its layer content to the image, and add a CALayer in which you draw the progress arc and CAShapeLayers or filled CALayers to draw the Play/Resume shapes. CALayers are light-weight and straight-forward to work with. You would capture the users touch in the usual way - with a gesture recognizer added to the UIView.
I personally find it is often easier to roll my own in a case like this than to deal with the integration of external projects, mainly because they tend to be much more general than I need, and the amount of work understanding how to integrate them, how to strip out what I don't need etc. ends up being greater than the work needed to make this component myself.
That being said, you should realize that if you roll your own, you have to debug and test thoroughly - whereas with third-party code you are (hopefully) benefitting from the testing of many other people.
For an introduction to CALayers, see the WWDC 2010 session "Core Animation in Practice - Part 1" (full disclosure: I was the presenter).

how to know the default properties' values of UI controller in iOS [closed]

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
how to know the default properties' values of UI controller in iOS?
Such as an alert view, I have Cancel/OK button on it, how could I know the Cancel/OK button's border color, border width, border's shadow?
And others, like button on navigation bar...
To sum up everything that's been said here - you can't get most of the data you need for the standard UI elements in iOS. You can however NSLog any of the UI elements and check out some of its properties. Be mindful of the fact that about 99% of the system UI elements have read-only properties meaning you can't change their look and feel directly (and honestly, you shouldn't).
Check out interesting projects like UI7Kit that allow you to port iOS 7 design to earlier iOS versions. Also Cocoa Controls are highly recommended for any UI customisation tweaks.

How to do Feedback form in IOS? [closed]

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.

Cascading Popovers: User Friendliness vs Guidelines [closed]

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?

Resources