What kind of documents should we upload for releasing the new app in Huawei App Gallery?
For both the individual as well as enterprise developer it is mandatory to provide copyright information if developers want to distribute the app in “Mainland China”. Publishing app to outside China it is not required to provide copyright information, but it is required to provide “Copyright Information(Disclaimer)” if you want to distribute a common app to the Chinese mainland. Similarly It is required to provide “Copyright Information(Software copyright and Copyright disclaimer)” , if you want to distribute a game to the Chinese mainland
Please check below document link for selecting the category and copyright qualification :
App Categorization : https://developer.huawei.com/consumer/en/doc/app/50103
Copyright Qualification : https://developer.huawei.com/consumer/en/doc/app/30215
Related
We're a marketplace that connects our contractors with customers. We want to release an iOS app (React Native) for our contractors but we don't want the app to be on the public App Store. For Android we use the Alpha Channel feature, which gives us a link that we can send people to download the app.
The Enterprise program isn't suitable for us I think because we can't ask our contractors to enrol in a program?
The Custom B2B program doesn't seem to be a good fit since we are not selling or white labelling any apps?
Is there another option or am I wrong with the above mentioned assumptions?
Options for Distributing Your iOS App to a Limited Audience
Imagine you’ve built an iOS app for a limited set of users. Since it requires authentication, the app is useless to the general public. Is the public App Store the only option to deploy this app without express shipping devices through the mail?
I’ve identified 5 options that you should know about.
1) The Public App Store
Distribute the app on the public App Store. Only people authorized to use the app can authenticate and use its features. Requiring a small price (such as 99 cents) will discourage casual installations.
Submitting to the public App Store requires an iOS Developer license for $99 per year.
Pros
Apple provides the distribution service – The App Store. It is highly available and well understood by users.
The App Store promotes your company on a highly visible marketplace.
Cons
The App Store approval process is required for initial app deployment and app updates. You may be required to make changes to the app. The approval process used to take weeks, but currently only takes a day or two.
The App Store provides information about your app to competitors including a description of the app’s features, screenshots and an indication when the app is updated.
If you charge a price for the app, 30% of the revenue goes to Apple.
2) iOS Developer Enterprise Program
The iOS Enterprise Distribution program allows a company to distribute their own “in-house” apps directly. It is intended for employees of the licensee company only and that licensee must be a company or organization with a DUNS number. The cost is $299 per year for this license compared to $99 per year for the iOS Developer License. A given device can have apps installed from only one iOS Enterprise License at a time.
*Note: The following is an excerpt from the iOS Enterprise Distribution License Agreement
“Internal Use Applications developed under this Agreement may be deployed on Deployment Devices in two ways: (1) deployment for internal use by Employees, and (2) deployment for use by Customers either on Your physical premises or under the direct supervision and physical control of Your Employees in other locations, subject to Apple’s right to review and approve such deployment as set forth herein.”
Pros
The App Store approval process is not required.
The general public cannot see a listing for your app, purchase or install it. It is not on the App Store.
Cons
The Enterprise program is intended for employees and contractors of the licensee only.
The licensee is responsible for distributing and updating the app. This can be done manually by email, making the app available on an Intranet site, through a Mobile Device Management System (MDM), etc.
The cost is $299 per year for the Enterprise Developer Account compared to $99 per year for the iOS Developer Account.
*Note: The Enterprise program does not enable you to deploy apps to the Public App Store. For that you need to be enrolled in the standard iOS Developer Program.
3) Custom B2B Apps Program
Apple has programs for volume purchasing and custom B2B apps. These programs operate from the online Business Store. The Volume Purchasing Program allows businesses to buy apps from the public App Store in bulk. Custom B2B Apps extend the Volume Purchase Program for custom B2B apps built by third-party developers. The third-party developer determines which Volume Purchase customer(s) can purchase a given app. Such apps are not available on the public App Store but only through the Business Store.
Pros
More convenient for larger distributions. Each individual installation does not require a user to make a purchase through the public app store and expense the cost. Instead, users are given a coupon that they can use to install the app.
Apple provides the distribution service – the Business Store. This provides some features of an MDM.
The general public cannot see the listing, purchase or install the app.
Cons
Requires App Store approval process for initial app and updates.
If you charge a price for the app, 30% of the revenue goes to Apple.
B2B apps are only available to businesses enrolled in the Volume Purchase Program. The Volume Purchase Program is limited to the following countries as of September, 2017: Australia, Austria, Belgium, Brazil, Canada, Czech Republic, Denmark, Finland, France, Germany, Greece, Hungary, Hong Kong, India, Ireland, Italy, Japan, Luxembourg, Mexico, Netherlands, New Zealand, Norway, Poland, Portugal, Singapore, South Africa, Spain, Sweden, Switzerland, Taiwan, Turkey, United Arab Emirates, the United Kingdom, and the United States.
*Note: An iOS Developer License is required to use the Custom B2B Apps Program. Limiting an app to the B2B App Store is an option when submitting to the Public App Store.
4) Ad Hoc Distribution (intended for Testing)
Ad Hoc Distribution allows you to distribute apps to up to 100 iOS devices for testing. You must register these devices manually by their ID. Devices can be removed/replaced once each membership year). Ad Hoc Distribution is a feature of both the iOS Developer Program and the iOS Developer Enterprise Program. This may be all that is needed for a prototype or trade show.
Pros
The App Store approval process is not required.
The general public cannot see the listing, purchase or install the app.
Over-the-air installation from a hyperlink (hosted on your web server or on an iOS Beta Testing Service *mentioned next) or by emailing to a computer with iTunes installed (and then installing to the device).
Cons
Limited to 100 devices (devices can be removed/replaced once each membership year).
The UDID (Unique Device IDentifier ) of each device must be associated with your provisioning profile. This is a manual process.
Your team must manage deployments and updates.
The related developer provisioning profile expires in one year. This means that the app will run on a given device for a maximum of one year. When the Developer Provisioning profile expires the app will need to be rebuilt with a new provisioning profile.
5) iOS Beta Testing Service: TestFlight
TestFlight is a free over-the-air platform used to distribute beta and internal iOS applications to team members. Developers can manage testing and receive feedback from their team with TestFlight’s Dashboard.
TestFlight makes use of your iOS Enterprise License or Developer License to create Enterprise and Ad Hoc provisioned apps.
Pros
The same Pros as #2 iOS Developer Enterprise Program or #4 Ad Hoc Distribution depending on which iOS license you use.
Distribution and feedback is managed with a free, cloud based service.
Cons
The same Cons as #2 iOS Developer Enterprise Program or #4 Ad Hoc Distribution depending on which license you use minus the Con about managing deployments and updates. According to Apple, TestFlight builds are only valid for 90 days. Apps cannot be opened after that period.
Other Testing Tools and Services
AppCenter: iOS, Android, Windows, MacOS and more.
Firebase App Distribution: iOS and Android distribution.
If you are not selling the app through the Apple App Store and have a target customer base, I would try the Microsoft App Center to distribute the app. It kind of works like TestFlight, but you don't have to worry about their review process.
Now we have one more option to distribute apps supported by Apple as the official way to do exactly what you are asking for: Custom Apps
Engage with businesses and educational institutions to design and build customized apps that meet the unique needs of their organization. With Apple Business Manager and Apple School Manager, you can privately and securely distribute to specific partners, clients, and franchisees. You can also distribute proprietary apps to your internal employees.
There is now (since a while back) another alternative to this problem: Unlisted app distribution
https://developer.apple.com/support/unlisted-app-distribution/
It makes it possible to publish your app on the App Store, but the only way to find the app is by a direct link.
And an important difference of this to Apple Business Manager is that you can distribute the app to both managed and unmanaged devices which makes it possible to let users buy there own devices.
I think that Unlisted app distribution is pretty new but will become more and more common when Apple now (2022) do not let companies with less than 100 employees renew their Apple Enterprise Developer Programs and force those companies to other distribution models.
Applivery allows you upload an app (Android & iOS) and distribute to employees or beta testing, without MDM or Google/Apple Store. They have a free trial...
I've noticed Pro features of Working Copy are available for free for students on GitHub. Does anyone know how I could apply this benefit?
Here're the instructions:
Pro features are available to students for free as part of the GitHub Student Developer Pack
Install the app from the App Store on your iPhone or iPad
In order to use pro features, you have to verify (do it on your iPhone/iPad) your GitHub student account
These pro features normally require a purchase, but are available for free while logged into your student GitHub account.
Always follow up-to-date instructions that are available here.
It is a mistake that this isn't clear from the Users' Guide and I will fix that.
Best regards,
Anders (that makes Working Copy)
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
I have created a nice icon for my app that quite accurately reproduces the style of Apple's Aluminum logos (ex. iCloud, etc.)
In reading the app review guidelines, I noticed this:
8 - Trademarks and trade dress
8.1 Apps must comply with all terms and conditions explained in the Guidelines for Using Apple Trademarks and Copyrights and the Apple Trademark List.
8.2 Apps that suggest or infer that Apple is a source or supplier of the app, or that Apple endorses any particular representation regarding quality or functionality will be rejected
8.3 Apps which appear confusingly similar to an existing Apple product or advertising theme will be rejected
8.4 Apps that misspell Apple product names in their app name (i.e., GPS for Iphone, iTunz) will be rejected
8.5 Use of protected 3rd party material (trademarks, copyrights, trade secrets, otherwise proprietary content) requires a documented rights check which must be provided upon request
8.6 Google Maps and Google Earth images obtained via the Google Maps API can be used within an application if all brand features of the original content remain unaltered and fully visible. Apps that cover up or modify the Google logo or copyright holders identification will be rejected
In particular 8.3 seems to say that you can't look too much like an apple product.
Will my app be rejected?
There are lots of apps that have aluminum icons. You'll probably be fine. But it is Apple. You never know. And changing the icon if they don't like it isn't a big deal. See what happens.
There is no way to tell for sure until you submit the app for review. Nobody can tell you what will happen except the people doing the reviews at Apple and you won't find that out until you submit it. I would submit it and see what happens.
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.