This might be a repeated question but I have not find the answer yet
suppose that i want to develop a new ios application that might be used with our customers to collect data concerning them.(for example take orders from outlets, survey data, make a a field inspection...etc)
the application uses a backend application server (developed by us) to login and download lookups data for the IPhone application (such as list of outlets, type of questions...etc). these data are specified previously by our customers though a web application.
my question is, will apple charges our customer of using such service? supposing that the ios application is free and published into apple store?
the application may have a trail account for use by other customers
regards,
Apple won't charge your customers for anything you don't charge them for in your application. If you sell items via IAP, they get a cut. If your iOS app is free and uses a service the user is paying for, that's fine. There are numerous examples of applications that connect to paid-for applications like Basecamp, FreshBooks, Harvest, GitHub, Evernote, and Netflix.
Related
Just to give you a little background, we have a software application which anyone can access through web. It is a very specific application for banking and retail industry. Currently this application is accessible on web as well as on "Windows tablet kiosk" and we have license based pricing. Windows tablets access the data through web services.
So for example, XYZ Bank can order 100 windows tablet licenses and we can charge them for the application based on our pricing model for 100 license.
We are getting lot of requests from our clients to develop the same app on iPad and we are currently researching on deployment options for the same. As per my understanding, Apple has very stringent rules when it comes to App download.
In above scenario, where organization needs a licence from us to run the application what kind of deployment strategy we should go with? I can think of 2 options:
1) To deploy the app on iTunes stores and ask the organization to download it from the iTunes store. They will have to contact us to get the license in order to run the App. Is it legal? Since we have license based pricing model, we'll keep our App for free and will charge organization for license.
2) Should we just get enterprise license for our clients/organization and deploy the system on their iPad under that enterprise license.
According to me option # 1 is the way to go. But I just want to know if this is OK to distribute the App for free and than charge for licenses? In any case this is more of a web app and iPhone is just an extension.
Option #1 is only ok in a special case, when you have a general subscription model for your service outside the App Store/IAP process, like Spotify does, for example. There's a special paragraph in the App Store guidelines for that, 11.14. But if your customers pay a one-time fee just to use the iPad app, I think Apple would consider this as circumventing the App Store payment model and would reject your app because of rule 11.1 of the guidelines.
But Apple just set up a new distribution model for cases like yours, the "Custom B2B apps". It's a way to distribute custom apps for specific customers through the App Store, without the need for Enterprise Licenses for each customer. See
http://www.apple.com/business/vpp/
Only customers that you have approved before will be able to see their custom app in the App Store. Payment goes through Apple and they keep 30% as usual. This program is US-only now but will be rolled out to Australia, Canada, France, Germany, Italy, Japan, New Zealand, Spain, and UK soon.
If you don't want to give the 30% away, your only option is indeed #2, building the app with an Enterprise License of your client. The only real downside I see is that you have to get each client to enroll in the developer program and renew it every year. If you have many clients, that could become a problem.
But once they've set you up as an agent or admin, the process is smooth. E.g. you can use a MDM service for OTA updates to your client's devices and they can set up an inhouse app store, so their user experience is almost the same as when using Apple's app store.
I've just decided to go with option #2 for an enterprise project for 3-5 clients. I would say that if you have more than about 10 clients, the extra work with all the different certificates, distribution methods etc. wouldn't be worth it and I'd rather pay Apple 30% to handle that and go with the Custom B2B program (if it's available in your country).
Option 1 is more preferable.
You can have a free app on the app store.
After that you can have a option for licensing. and from coding you can maintain that in order to use the app they needs to purchase the license.
Lots of app does that as they have their signup based on the Device ID.
I have worked with some of the apps who uses to give their services like SIP Calling with licensing like that.
so with option 1 you can achieve it.
thanks
My company bosses want to create a native version of a currently web-based app that will be available to their existing customers (currently a few thousand).
They say it is imperative that the application be available for downloading from the app store.
However the app would only be of any use to customer who already have an account (and would be useless to anybody else who downloaded the app).
Is this actually possible to submit such a thing to the app store?
There are dozens of Apps in the App Store that where they are only usable if you are an existing customer. Look at all the banking related ones for example.
AFAIK, you cannot restrict the intended users when distributing through the AppStore.
What you can do is apply for an iOS Developer Enterprise Program, though you'd be installing the app directly to the devices (requires physical presence of the devices).
You could also use a service like TestFlight, though their terms probably just allow deployment for testing purposes.
What I'd go for is getting the app to the AppStore anyway, as long as your app doesn't include confidential content. You could advise in the description not to install the app unless they're your company's clients.
The app that I am trying to submit is for a field sales system that is already running on Android devices, and which we are now trying to make available to Apple users. It is a cloud based application, and users synchronize data stored on their devices with data stored on a web server. The application is sold to companies rather than individuals. Each company has many users, all of whom synchronize with the same database on the server.
We maintain our own web server and provide a hosting service, and companies can also host their own servers:
For the hosting service, companies pay a monthly or annual fee, which depends on the number of users they have.
For companies that prefer to host their own servers, the app is licensed by device. Companies pay registration and upgrade fees for each device, and each user has to enter a registration key.
I understand that we are not allowed to mention the Android platform anywhere in our app. I also understand that we have to allow all subscriptions, registrations and upgrades to be paid through in-app purchases. But I have a number of questions:
I am happy for us to offer only a limited service to Apple customers, if it makes it easier for the app to be accepted. Would Apple be happy with this arrangement?
Most companies prefer to have just one administrator for their whole system, and to have him make all the purchasing arrangements. Is Apple OK with this?
Is it possible to make multiple in-app purchases of a single product (e.g. purchase 50 licenses)?
Is the use of registration keys an issue?
1) I think that as long as your clients are aware that the iOS flavour of your app/service was limited in some manner (tell them the rest is work in progress) then I cannot foresee any issue with this. You may still consider ringing Apple Developer Support and run it past them, but your chances of getting a non-vague answer from them directly are still high - they'll probably say it depends on the reviewer when you go to submit the app.
2) Sounds fine, and not uncommon in the enterprise app world. See 3) for more details.
3) You can utilise the VPP (Volume Purchase Program) to achieve this, but it's only available in the US at time of writing. See the link below for further information:
http://www.apple.com/business/vpp/
I think that another way you could consider app distribution and which would let you bypass Apple (to a degree) is to sign up for an enterprise developers' account. This will let you build the usual development & distribution builds of your app, but a distribution build can take two forms: limited to devices by their UDID (100 limit still in effect) or not at all. If the latter, you could self-host the generated .ipa app file, which is perfectly viable.
4) Registration keys for the app? (to unlock "premium" content or as the method of app activation?)
Hope this was of some help, best of luck!
I'm going to develop an iPhone app, and want to make sure what I want to do is possible, and will be approved by Apple.
I'm going to create an app that will be fully branded on per submission basis. I want to have one app per customer (our customers are companies) with their logo, skin, etc.
This apps will be downloaded and installed by the employees of each one of our customers.
In other words, we would use the same base code (logic doesn't change), but will brand it for each customer. Something similar to what Magento (http://www.magentocommerce.com/product/mobile) does, they created an Ecommerce mobile app, and they brand it to their customer, but the app logic remains the same.
Would Apple consider this as duplicate apps? what is the best way to do it?
Thanks in advance.
I would have said "no problem" until I read:
This apps will be downloaded and
installed by the employees of each one
of our customers
It sounds like what your creating is (a set of) private applications, which are intended to be targeted only to specific users - i.e. employees of the company.
Apple has a separate "enterprise" development program geared towards this - allowing developers to deploy programs for their own company - and do it outside of the App Store.
If your program is very specific towards the companies, Apple may make you do this - rather than putting the Apps up for general consumption on the App store.
See here for more details:
http://developer.apple.com/programs/ios/enterprise/
Also:
If your application is really intended for a wider audience, and your could in-fact sell/distribute it a such - you could "skin" the app dynamically. For example, on first-time launch, when you "register" with some "service" - based upon your email address it could download the appropriate skinning graphics.
I can say I know of several companies built on this strategy. The code doesn't change one iota from app to app, only images and names change and they continue to bring in revenue.
EDIT: Note this is against apple policy and if they find out they have been known to ban accounts. They consider it spamming and prefer that you sell one app that provides in app purchases. Directly from their feedback on a particular group of app submissions:
Thank you for submitting your
Photography apps to the App Store.
We've completed the review of your
apps, however, we are unable to post
them to the App Store because they
provide the same feature set and
simply vary the content. Apps that
replicate functionality with different
content create clutter in the App
Store, hindering users' ability to
find apps, and do not comply with the
App Store Review Guidelines
https://developer.apple.com/appstore/resources/approval/guidelines.html:
2.20 Developers 'spamming' the App Store with many versions of
similar apps will be removed from the
iOS Developer Program
You can now use Apple's Volume Purchase Program to release differently branded versions of the same app to different customers. The app can be free or paid. Each customer must have a DUNS number (Dun & Bradstreet). See the FAQ for details.
We are developing an enterprise application and I looked at the following options:
1. Putting on itunes.
Cannot do this since our application is to be used only by our clients with a login and passwrod.
You cannot have login based app in itunes:
http://appreview.tumblr.com/post/952395621/cannot-be-intended-for-a-limited-audience
2. Using iOS Developer Enterprise
Cannot do this as :
The iOS Developer Enterprise Program should be used to develop and distribute proprietary in-house applications to your own employees within your own company. As such, your company would not qualify for direct Program enrollment in this situation. We would suggest that your client apply for enrollment in the Program, and, once enrolled in the Program, your client may add the appropriate developers from your company to their iOS Development Team.
Our client cannot add us.
3. Adhoc distribution.
This is only for 100 beta testers.
So are there any other options if I want our client to donwload our app.
Provide some minimal functionality to all users that does not require any proprietary data, but have the app download all proprietary data and enable proprietary features only after your enterprise customer logs in. Then submit it to the App store.
There are plenty of examples in the app store. Banking apps: they might advertise the bank, have maps to the nearest branch, perhaps include a calculator of some sort, but of course don't allow any actual banking features or download any account information until after a customer logs in. Security apps: provide a public weather web cam view to everybody, but a security cam view only to people who buy their expensive $100K security camera system.
The example private golf course app could have included public information on the club, the current weather, map info on local restaurants, and maybe who to contact to apply for the $10M membership, but then added private club info (calendar, roster) only to paid members after log in.
Make sure to create a test account with dummy (non-proprietary) data and give it to Apple.
You can absolutely have a login based app. I have helped someone submit one that got approved that sounds very similar to the one you are describing. Also, think about the Netflix app for example, login based, limited to Netflix users (although this is probably not as limited as you are talking about).
Your solution is clearly "Using iOS Developer Enterprise"...
Can you be more explicit about the "Our client cannot add us." ?
You can get your client to sign up to the iOS enterprise agreement so that they can install it on their phones, and you are simply a team member for them. That also shifts the liability for the app onto them, should anything go wrong.