I'm unable to change the price of an in-app purchase. I added initially for testing purposes, but now that I'm submitting the app, I'd like to change it. Unfortunately, it doesn't seem to accept the change. It is showing me the same price tier not the updated one.what should i do ?
I had this problem too. Here's how I solved it.
When you change the tier in iTunes Connect, it's not enough to then click 'done'. You need to set the schedule to 'Now' and 'None' (for start and end date) and then click the 'Add to schedule' button. Then save.
Cheers,
S
I found this especially confusing as the "Add to Schedule" button is disabled in my browser, even after selecting "Now" and "None". The button only becomes clickable after clicking on the background of the page to deselect the dropdown, which is probably firing some Javascript event that understands to enable the button.
Just to make it painfully clear (because I was still doing it incorrectly, even after reading Stew's answer above), here's a screenshot.
You need to:
Select a tier.
Select options from the 'Price Effective Date' and 'Price End Date' menus (use Now and None for a price that's effective immediately and indefinitely).
Click 'Add to Schedule' (it's easy to miss this step).
Click 'Save'.
This is now much simpler than it was when the question was asked originally. The Features page for your app at App Store Connect has a Plan a Price Change button under your in-app purchase, and when you press that, it’s very clear how to schedule a price change and make it take effect.
Not sure if anyone is here in 2020, but this is now in the "In-App Purchases" side menu. I tried twice scheduling a price change, and it didn't happen both times. I came here and saw there was something to do after you click "done", which is obviously much different now, but there is something else you need to do after you click "done". You need to also click "save" in the top right.
Related
I am trying to create Adobe Captivate Quiz and have included Drag and Drop Interactive Questions (along with MCQ questions). How to go to the next slide?
I have changed the text of 'Submit' button to 'Next' button. In 'Drag and Drop' Actions, I have selected the following settings:
The question looks like:
The correct answer to this question is 'provide a safe workplace/environment'. When I try to submit a wrong answer or no answer, and click on the 'Next' (Submit) button, the control does not go to the next slide.
I tried to keep these settings:
This setting simply gives me 10 attempts to submit right answer. Without going to the next slide.
What settings should I choose and how do I move to the next slide and ensure that the candidate has the freedom to revisit the question n number of times, until they 'Submit' the entire quiz?
Thanks in advance :)
Drag and Drop slides are Content slides and not Adobe Question Slides and hence, changing the number of attempts will not necessarily help.
Number of attempts simply means the number of attempts to reach the correct solution. This means that they will have say 10 attempts to select the correct answer. However, they not be able to proceed to the next slide unless they get the answer right or they are out of attempts.
The best way to implement such questions will be using dropdown Fill In The Blanks or Sequence questions.
Hope this helps!
I've seen how iphone users delete from lists - its generally a swipe action and then shows some minus/remove button.
I realize that it is counterproductive to implement iphone things on android because android users don't know this stuff.
I don't want to do that, I just don't know of a better/intuitive way to delete from a listview.
I've previously opted for doing "longclicks" on listview items, which will show an alertdialog asking if you want to delete or do other things, but this is never an obvious thing to do.
I've seen delete buttons that are shown in each view, but that messes with the layout of the listview, in a way that wasnt' considered in the wireframes.
What is a good intuitive way to allow the user to remove items from listviews on android?
Here's my two cents before I pitch my answer. Any one who has an android phone is going to know or eventually find out that longclicks often lead to another menu. Yes, it's not immediately obvious but they are going to figure it out just as iphone users have figured out the swipe action is to delete.
If you really want a fool proof way for a user to know how to delete, I would implement checkBoxes. (More on check boxes here)If the user checks the item, bring up a "soft menu" at the bottom that has a bunch of options normally associated with long clicks.
If you look at the gmail application and check a box, you'll see what I mean when I say "soft menu".
Another way you could go would be to implement check box, then have "menu options." Every android user should be able to see and figure out the menu button on their device, all devices have them. Make one of the menu options delete and you're all set.
http://developer.android.com/guide/practices/ui_guidelines/menu_design.html#options_menu
I agree that long click is horrible, but it is the standard on Android; people are more likely to be able to discover using this than any alternative gesture.
Also, put in a delete menu item on the Activity you get to after selecting something from the ListView.
In my view you should add checkbox to your list view and give a separate button for deleting items from list I mean to say that add a delete button in the layout in which your list view is also present and when user checks the item which he/she wants to delete and click on the delete button,the item which is checked by the user gets remove from list.
I am trying to find the most usable/accessible way to implement a simple form dropdown list which will sort a list of products by pice and alphabetical order.
In your opinion is the dropdown more usable when there is a button that governs its submission or when it automatically submits onchange of the dropdown?
The research I have read is both for and against such methods and there is a variery of implementations on the web so interest to hear the thoughts of the community.
Thanks in advance
As a blind computer user either method works fine. I find that having a button to click is slightly easier for me then the onchange event firing. I wouldn't say it's a big enough difference to take into account though assuming the majority of your users will not be disabled. If your targeting specifically blind users I would not use the onchange event.
So long as you do not change focus or navigate to another page when the selection changes, either approach should work. The classic example of a problem dropdown is where it contains a list of other pages on the site, and navigates as soon as the selection changes. This prevents a keyboard user from using the list; they can't browse it, and can't navigate to any pages beyond the first selection, since it's impossible to navigate past those. So in cases where focus changes or the page navigates as a consequence, having a separate action (eg. Go button, or handling enter) to cause the navigation to take place is essential. This is likely where the advice you've read is coming from.
In this case, however, it sounds as though you are just updating content elsewhere on the page, and not changing focus or doing navigation. Simply resorting existing content should be fine.
Depends on your users and their respective expectations and the context in which it's presented.
As a blanket, general statement, you should have the drop down accompanied by very obvious submission button. That is the safer approach.
If you are refreshing page data or if the focus moves away after the dropdown option is selected, you should use a button to be accessible. If you fire the event on change, blind or keyboard-only users will not be able to use the dropdown menu at all if they are on windows with ie and chrome (so added together, a majority of the people on windows). As soon as they use the arrows to scroll down and make a selection, the first option they hit will be selected and the page data will refresh or the focus will move, making it impossible for them to navigate or select the second option, third option, etc. Below is a thorough explanation with examples so you can see what I mean.
Designers definitely don't like the buttons, but if you are blind and on chrome/ie, it is impossible to use a lot of dropdowns without it. I'm guessing Jared uses firefox or a mac.
http://pauljadam.com/blog/javascript/onchange-event-on-a-select-inputjump-menu-accessibility-problems/
I am compulsive and like visually clean designs.
Theres a pop up in my app that tells the user that there's an error.
I made a clear button over the entire pop up (about 200x100 px) so the user can just touch the notification to dismiss it.
But i'm afraid the user might not know that you can just touch the pop up to dissmiss and would go crazy looking for the "OKAY" button.
Do you guys think the OKAY button is necessary or is a giant clear button overlaying the notification good enough?
note: the whole notification actually looks like a button because of rounded corners and some button like borders.
Whatever users can misinterpret, they will (just look at some of the low ranked App store reviews for examples).
So, unless it clutters your UI and/or makes things even more confusing, a clear indication of how get rid of or move beyond your popup will certainly reduce the chances for any user confusion.
I like the idea of your design, but I would go for an OK button. There might be people in the world who don't understand it and blame your app.
Or you leave out the button and make the notification disappear by itself after, say 5 secs.
Or you could go the Microsoft way:
- add the "Okay" button
- add a smaller checkbox with the caption "don't ask me again"
- when the okay button is clicked and the checkbox is marked, open an additional dialog notifying the user that the Okay button will no longer be displayed, but that they can clear that setting in the preferences menu
- create the preferences menu as described
Now who says Microsoft suck at UI ?
You should use the OK button. Not only will it be more familiar for users, but you won't have any problem with Apple's approval process. Depending on the reviewer they might reject the app for not conforming to the Human Interface Guidelines.
In the Preferences app, Safari's settings page contains buttons labeled "Clear History" or "Clear Cache". The Mail App's settings page contains a big red "Delete Account" button.
Is there a way to create such a settings page with buttons for my app? I checked Apple's documentation and didn't find an element type for such buttons.
Sadly I think you're out of luck - unless you jailbreak. To create the Settings page for your app you create a plist rather than actually coding the view itself. This brings certain restrictions such as the inability to add a button. The one core thing you can't do is to execute any code from the Settings app - all you can do is change a set of preferences.
The closest you can get is to add a switch with the label "Clear History on next starup" and check whether the user has set this whenever you start the app. Then set the settings so that the switch is set to Off.
AppStore apps — You can't. Even if you can add a button, no code can be run, making this useless.
Jailbroken apps — Use a PreferenceBundle and create a PSButtonCell specifier. See http://www.iphonedevwiki.net/index.php?title=Preferences_specifier_plist.