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 a Keyboard extension for iOS. One of the requirements I have is to provide a functionality in which the keyboard's design and word prediction capabilities are temporary. Meaning after a month/45 days I want to change the keyboard looks and disable the word prediction capabilities until the user buys those again using the in-app purchase mechanism.
Basically I want to provide the app for the user for a trial period after which the application becomes less functional.
I have implemented those behaviors in the Android app and now I'm required to perform the same functionality in the iOS app.
The question is: Is this type of app behavior is allowed by Apple, or will I be rejected for this?
The Answer is No, You can't Publish trial Base Apps.
As per App Store Review Guidelines :
2.9 Apps that are "demo", "trial", or "test" versions will be rejected. Beta Apps may only be submitted through TestFlight and must follow the TestFlight guidelines
Possible Solution:
I Don't know what features you have in your App. But this might help you.
You can use Subscription based inApp purchases where user can purchase & enable some feature & that will be available for some limited period.
For more details check out here: https://developer.apple.com/in-app-purchase/
Hope it will help you.
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 6 years ago.
Improve this question
I am new in ios development. I have created one app, in this app some features are not available right now. So my question is can i submit my app to app store with same design by giving coming soon alert for those features. Thanks in advance.
It is likely that your app will be rejected if you include such an alert. Refer to section 2.1 of the App Review Guidelines:
2.1 App Completeness
Submissions to App Review should be final versions with all necessary metadata and fully functional URLs included; placeholder text, empty websites, and other temporary content should be scrubbed before submission. Make sure your app has been tested on-device for bugs and stability before you submit it, and include demo account info (and turn on your back-end service!) if your app includes a login. If you offer in-app purchases in your app, make sure they are complete, up-to-date, and visible to the reviewer, or that you explain why not in your review notes. Please don’t treat App Review as a software testing service. We will reject incomplete app bundles and binaries that crash or exhibit obvious technical problems.
And
2.2 Beta Testing
Demos, betas, and trial versions of your app don’t belong on the App Store...
You should remove all reference to "future functions" and put it back in when the function is available.
Yeah, as per my knowledge you can submit but it must not crash on iphone or ipad and must follow all the guidelines of apple. Because coming soon is on kind of UI of your app so i don't think that it will be rejected due to this kind of stuff.
You should refer App Store Review Guidelines for more details.
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 6 years ago.
Improve this question
I've read through Apple's iOS app submission guidelines, although my question is more in regards to the rules (if applicable) after it's been approved.
Basically what I'd like to know is if a developer is allowed disable certain functionality in an older version of an app so that the user is essentially forced to upgrade to a newer version? This could also include making the user download another completely separate app (that the functionality was previously in the old version) in the process.
Is this allowable, or is there something that specifically says that's against the guidelines/rules? If anyone knows the answer to this and could provide the source of the info that would be great. thx.
You can't force user to upgrade app but if you want so or there is no other option then you can launch the App Store so that your users can get the latest version from there. or you can display some UI which does nothing except giving update option!!
[[UIApplication sharedApplication] openURL:[NSURL URLWithString:iTunesLink]]; //your app's itunes link to open it when user open the app
You can refer Apple forums and can check this answer.
hope this will help :)
Do you really think anyone would download the new version? Customers would swear at you and find a different app. If they paid, they will ask for a refund, and Apple will give them the full refund. Since Apple only gives you 70% of the sales price, and the full refund comes out of your pocket, a full refund will cost you real money.
Apple's interest is in selling phones. You are welcome as long as you help them selling phones. If you are an ass and upset Apple's customers, Apple will do what they can to upset you.
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 7 years ago.
Improve this question
I was just wondering what are the guidlines and policies about updating an app on app store? Are we allowed to enforce the users to upgrade their applications programatically?
I'd like to give you some key-points, that might be useful in yours app-update strategies.
Non forced update: (1.X.X) You can use this strategy when you updated your app slightly and updating to it will provide user more delight product. Then you might use simple UIAlertView with notification about new version update and it's features and OK|Cancel buttons, that lead to appStore. This notification can be shown, for example, every time user launches the app. Every applicationDidBecomeActive call can ask your server for actual information about new version
Forced update (2.x.x) you might find it useful, when you made breaking changes on your server-side or you decided to stop supporting some old versions of the app. Then after server-call and retrieving information about app deprecation a modal viewcontroller can be shown with only button, that leads to AppStore and text, that informs about new version available.
Both of these scenarios are used in my apps, and I've never had any troubles with Apple's policies.
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 9 years ago.
Improve this question
I'm making a game on iOS, and I'd like to know if it's possible to make a "pre-order" on my app.
Example : I want to release my game on May. Is it possible to publish it on March but just for "pre-order" ?
It's a good way to see if the app is appealing or not.
The iOS app store has no such functionality. You can only make it available or not, there is no "pre-order" status.
No, it's like "demo", "beta" policy and so on. You cannot do this in AppStore.
No, that's not possible.
You can only release apps that are fully functional.
That's why you can't release beta apps.
This is not possible. If you want to "test the waters" and/or build "hype" best thing you can do is create a landing page website with a good app description/image and see how many people are willing to leave their emails on your entry form.
Then on launch day you email blast those people.
If the app doesn't work or look like a beta, you don't have to call it a beta in the description sent to Apple. If your app is complete and good enough for Apple to approve it after it's submitted, you still don't have to release it immediately. When in the approved but unreleased state, you might be able to use up to 50 iTunes redemption codes to allow further reviewing of your app.
Before you can update the unreleased app, you might have to release it for a couple hours at 3AM in only Monte Carlo or equivalent.
You can use a service like TestFlight to release a Beta to a limited number of people (I think you can release to a max of 1000 with TestFlight)
More information on TestFlight here - http://www.testflightapp.com/
Apple inc. has strict guidelines for App submission and it review.
You can have a look at this.
You requirement for pre-order app submission violates oint 2.9: Apps that are "beta", "demo", "trial", or "test" versions will be rejected.
This link will give you more insight on the process.
So you have to either cut-short the game of yours and submit it as full-functional app. Apple doesn't care how much level your game has. And in later on-releases you can add the levels and updates. But make sure you adhere with the guidelines and do not display the "demo/trial/etc".
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 10 years ago.
Improve this question
Here's my situation: I'm making an app for iPad which uses image libraries. The app comes with a few libraries. I want to sell additional libraries from my website. An image library contains only png files, nothing else.
The app will have an "Activate" button so if the user buys an library they can activate it from within the app. The app connects to our server via web services and validates the activation code.
The image libraries (since they can be huge) are copied in iTunes to the documents directory for the app.
My question is: does Apple have a problem with allowing me to sell additional image libraries on my website and have the user activate it and copy the files to the documents directory within the app (which I expose within the app) or is this an infringement of their policies?
Thanks in advance
Edit: Because #Kris Gellci was so eager to prove he's answer is correct, I took the time and search for the exact paragraph in the App Store Review Guide which speaks about this.
11 Purchasing and currencies
11.1 Apps that unlock or enable additional features or functionality with mechanisms other than the App Store will be rejected
11.2 Apps utilizing a system other than the In-App Purchase API (IAP) to purchase content, functionality, or services in an App will be
rejected
11.3 Apps using IAP to purchase physical goods or goods and services used outside of the application will be rejected
This way you can see for yourself if it applies to you. There is more here.
Yes, they have a problem with that. You need to use in app purchases so that they can take their share out of what you sell. Think about it this way, if they would allow it, everybody would put their apps free with content and unlocks paid and Apple would be left out. More details here.