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 11 years ago.
Improve this question
I'm developing an app which I will duplicate to many clients. Each client will have one app on Apple Store.
For each version (each client) of this application do I need to create a new app_id/provisioning or can I use the same app_id/provisioning?
Cheers
Yes, you will need a different App ID for each application.
If you use a wildcard then you don't need to have a different app ID and provisioning profile. That is unless you want to use push notifications for example in which case you will need a specific app ID for each app.
That's assuming you're releasing the apps under a single developer account, of course. Multiple developer accounts then obviously you would need multiple app IDs and provisioning profiles.
It depends on what your app does, and what your future plans for the app are.
If you don't do push notifications AND don't use iCloud you can use a wild card as opposed to an app iD for each app.
Having an app ID & provisioning profile per app is cheap (as in no money).
Having a developer account per app would cost money, but if you ever want to sell an app (and the app's user base) independently of your other applications you will need to do that. Otherwise you will either sever the code from the user base when you sell it, or forever have to take code from the buyer and submit it to Apple on their behalf.
Related
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 need to develop an application for a Client who later wish to install this app, customize iPad wallpaper and some other stuff to suit to business needs and send it to his Customers.
The tricky part is I can not suggest him to distribute this application via Adhoc Distribution (Using Normal 100 device limitation account) as He says apple itself is one of their potential customers.
Enterprise Distribution isn't required for reasons that His company does not entitles for this developer program.
Now my question is If I go for B2B distribution model - The end user are essentially not the one who will download the application rather my client himself will do that and give them preinstalled application on iPad.
What options do I have here ? Any help suggestion will be appreciated. I have already gone through the various volume Purchase programs documentation but I could not figure out if B2B distribution exactly matches my requirement or not.
So, let's see if I'm understanding this:
You are making an app for someone else. We'll call you the 'developer'.
Your customer is paying you to build that app. We'll call them the 'publisher'.
The publisher will not be selling to the public, they will instead be installing the app on devices, configuring them and then selling the entire solution (i.e. device and pre-installed app) to their customers (we'll call them 'end users').
Yes? And since one of the publisher's potential end users is Apple, you have a heightened sense of compliance with the rules (which you should be doing anyway).
So in this case, the publisher distributes the app via the B2B model and makes themselves the party it is allowed to be sold to, restricting the availability to those devices. This will require the publisher to create an Apple ID to manage their VPP participation.
Now, that's assuming the end users aren't going to be using these iPads for other functions. If they are, then you'd need to allow those users direct access and perhaps re-figure the business model a bit. That would also allow the end-users to re-install the app if they needed to, etc...
This PDF described the process in more detail: http://images.apple.com/business/docs/vpp_business_guide_en_20130413.pdf
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
My App is rejected by the reason :
"We found your app inappropriately unlocks or enables additional functionality with mechanisms other than the App Store, which is not in compliance with the App Store Review Guidelines"
"It may be appropriate to revise your app to use the In App Purchase API to provide content purchasing functionality. "
What I have done is as below:
As this app is for my specific customer companies to use, I only want the companies who get the Invitation Code from me to use my app. There is no charge. I don not know is it necessary to use the In App Purchase API instead? if it is true , can you give me some tips?
Your application cannot be used by members of the general public, and thus does not belong in the App Store.
If you only intend your application to be made available to a few specific people, you should use Ad-Hoc Distribution to make it available to them.
Explain the purpose to the review team, sometimes they listen.
Also, maybe have that message as a "login page" instead. Have a username and password rather than a verification code. The verification code message may look more like you are selling the app behind the AppStore. Also provide the review team with an access code / login details if you haven't already so they can actually review the app.
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
I created a Newsstand App creating Mag+. All is pretty and works great, but the app was rejected for the reason of
"We found that your app has an associated free subscription, however, it does not include a mechanism for the user to sign up for the free subscription.
It is required to revise the app to include the mechanism to allow user to sign up for the free subscription."
So what are the exact steps to set up a free subscription?
Please DO NOT just copy an Apple link and say "go here," as none of what they write makes sense.
NOTE: this is using another service for the building process, so there's nothing I can do about the internal code in the app, just the itunesconnect settings.
THANKS ... every time you help me you save a kitten!
A free subscription IAP (In App Product) need to be created in iTunes (developer account) for your app just like any other IAP and there must be an option in app from where user can see that subscription and select to subscribe.
It seems like there is no option (like a button "Subscribe for Free" etc) in your App to subscribe to your magazine. Subscription availability is required by Apple for all Newsstand apps. On tapping Free subscription option (e.g. a button) a normal In App purchase (though free) should happen.
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
I developed an app for the company who sells professional e-books by their website. In order to keep the content in sync with web data, app enforce login/registration and without that doesn't provide any functionality.
This is the reason why it has been rejected for Review Guidelines 17.2 Apps that require users to share personal information, such as email address and date of birth, in order to function will be rejected
My question is: is there a way to convince Apple to accept an app?
It is directed to the very specific proffessionals.
In the future the company want to add the possibility to sync books available on their website.
Also the books bought by in app purchase would be available on their website for the user account.
Isn't that enough reasons for Apple to accept this app? My client strongly want to have an account based app, the whole system was designed for that.
There is possibility to track user by udid but still it is not good solution because it is deprecated and Apple rejects apps using UDID for tracking reasons.
Does anyone have similar situation recently?
You say:
"app enforces login/registration and without that doesn't provide any
functionality."
Apple says:
"Apps that require users to share personal information in order to
function will be rejected"
So the answer is kinda obvious.
The app should provide (at least) some basic functionality without sharing personal data.
Maybe some book previews? 1 or 2 free books? App info? Why not apple's-bookstore? Does the website (before seeing anything) force you to signup too? Otherwise just make a web-app.
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 11 years ago.
Improve this question
The scenario:
My company develops an iOS app for company A. Only employees of company A use this app and it must not appear in the Apple app store. Customer A pays us for developing the app, but the app itself is free.
The problem:
How do we distribute the app and updates to the employees (>100) of company A?
How the perfect solution should look like:
Like distribution through the app store: Company A doesn't need to do anything and the users can acquire/update the app easily and quickly.
Notes
Customer A wants to do as little as possible. They also don't really care about costs.
My ideas so far, please let me know what you think about them
My company applies for the iOS Enterprise Developer program (EDP) and puts the app on our own, login-protected website. Customer A doesn't need to do anything and its employees can simply download the app from the website.
Like 1., but customer A applies for the iOS EDP
The first method would be perfect, but according to this thread it might be dangerous. Though I highly doubt Apple would press legal charges (Free app, relatively low number of users, companies located outside the USA), I really don't want to take that risk.
Therefore, I'm currently favoring the second method. It might be some effort for Customer A, but it's still convenient for the users and it doesn't violate the EULA as far as I can tell.
My question:
Are there other methods to distribute the app that make sense in this situation?
Especially one that doesn't force our customers through a relatively complicated application process (most of them don't have a DUNS number).
There are several ways to do that. Here are some of them:
1)Fake code sign your app and jailbreak the devices you want to install it;
2)Create a web app instead of a native app;
3)Use Apple's B2B program;
4)Use enterprise distribution;
In my opinion only your second approach is applicable. In my opinion the company should decide whether they want to have an app or not. And if they have enrolled the Enterprise Developer Program they can have as much app as they want.