I have been thinking about submitting an app for my company, and it would serve as a simple app to get contact information easily.
But the question is, how much info to I actually need in the app to get it through the gates of appstore?
Currently the app is including:
- Different companies within our organization
- Small infotext about each
- Email button
- Phone button
- Contact persons, which leads to another view where I have contact persons with pictures, names, and direct phone/email buttons
Is this enough or do I need to include more features?
You can even add a app with single feature which is useful for the apple users, The only thing is make sure your app doesn't violet any of the app review guidelines and while preparing your app for submission on App store, in meta data information specifically mention that your app is for your orgnization's personal use
You will find apple app review guideline at following URL:
https://developer.apple.com/app-store/review/guidelines/
Related
I don't know where to answer these questions. I uploaded the answers in app review information note section but didn't work. What should I do?
The review message is attached below.
Guideline 2.1 - Information Needed
We’re looking forward to continuing our review, but we need a bit more information about your business model and your users to help find the best distribution option for your app. Our preliminary review of your app suggests that your app may be a good fit for our Apple Business Manager program, which is designed specifically for business apps.
Next Steps
Please review the following questions and provide as much detailed information as you can for each question.
Please describe which kinds of users you expect will use your app. Some common kinds of users are:
Users who are part of a single company (including its partners, employees and contractors)
A limited number of companies which are clients of the developer
The general public
Identify the specific countries or regions where you plan to distribute your app.
What features in the app are intended for use by general App Store users?
How do users obtain an account?
If there are any paid aspects of the app, such as for opening an account or using certain features in the app, please explain how users access the paid content.
Who pays for the paid content?
Since your App Store Connect status is Metadata Rejected, we do NOT require a new binary. To revise the metadata, visit App Store Connect to select your app and revise the desired metadata values. Once you’ve completed all changes, reply to this message in Resolution Center and we will continue the review.
You need to navigate to the app in Appstore Connect, click on "Version History" and then click on "Resolution Center". On that screen is a form where you can reply to the inquiry from Apple. It took me longer than expected to find it.
Apple developers rejected my app with this reason.
"Business - 3.1.1
Your app includes an account registration feature, which is considered an access to external mechanisms for purchases or subscriptions to be used in the app.
This feature does not comply with the App Store Review Guidelines.
Next Steps
Please remove the account registration links and any other fully qualified links to your site that could indirectly provide access to these mechanisms, such as links to web pages for support, FAQ, product or program details, etc."
The users can use the app in demo mode (without registration) with some restrictions, but if they register they can use without registrations.
The registration is not in webview. The client sends the user's datas to server.
Can someone help me?
You basically have two ways to solve the problem.
1) Sell the subscription etc. only through the App Store in the app (similar to Dropbox/Office etc.), i.e. there should be no links to your website, where your users have/can insert payment information. Look at the mentioned examples, how they solve this.
2) Only sell the subscription/services via the web, but never ever link to these pages via your app (similar to Kindle app, partially Spotify).
Your app must still be somehow (open for interpretation) functional for users without a subscription / registration.
The main issue Apple has, is that it's possible to circumvent the store and Apple's 30% cut. Just make sure that users are not able to purchase any digital products & services
Apps may not include buttons, external links, or other calls to action that direct customers to purchasing mechanisms other than IAP.
Source:
https://developer.apple.com/app-store/review/guidelines/#payments
Yes, You can submit app again but you have to implement one small feature like as guest user login.
In this You will implement one UIButton it's should say "Go without login". Implement this small functionality in your app. Create one user as guest.
When user hit "Go without login" you will pass your static user id and login in the app.
I have same problem. I am create a this solution and it's work
We're a small company and have developed an iPad app we would like to give to our customers. I've read through the B2B option but don't like our customers having to register their DUN info with Apple.
Should I just load it in the App store and put in the description that it's a private App? It requires a login so it doesn't matter if other folks download it.
Currently, we're using it in house via the internal tester scenario.
No one but Apple can say for certain what Apple will do in any specific case, but your description suggests it will be rejected.
From Apple's App Review Guidelines (https://developer.apple.com/app-store/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
If you don't have a base functionality that applies to the general public, you will, in all likelihood, need to go Enterprise delivery.
Distributing publicly might be the best option, but I don't think you would get an approval if you describe it as a private app in your description.
Without knowing too much about your business or the nature of your app, it's hard to suggest, but possibly you could add some public usefulness on the front-end of your app, even if that's business info, contact information, a news feed, etc... with the real intent of the app being tucked behind a login portal. (all total speculation).
Distributing the app outside of the app store has a lot of limitations as well: http://mobiledan.net/2012/03/02/5-options-for-distributing-ios-apps-to-a-limited-audience-legally/
I would just submit to the app store and see what happens. Apple may reject it, but that is true in any case. I have an app of this nature, submitted with a couple of test accounts, no problem getting it approved. When the app launches, it pops a logon screen, and has a short message about where to get an account (which won't make much sense to people not in the intended audience).
I have created a course site, let’s say 10 courses. Each price is $1.00. Now I have each course have ios application. If user pays for my course from desktop site, they can use same course from application also.
Now see, if user has downloaded my free app. If user wants to purchase, I have put up a link which redirects user to my desktop site and purchase course. Once he purchased course, he will be back to ipad app and learn course.
In short apple will not get its 30%. Will these going to be approved by app store when they don't get their 30% cut
The rule is pretty easy, the hard part is how Apple review team will understand the contents that you provide in your app.
If your contents can enhance or complete the app somehow and is distributed in a digital format Apple will require the integration of In App Purchase.
I remember that I've read from a blog a case similar to yours. The writer was complaining that the review team was constantly rejecting its app, because it was selling a CDROM containing an HTML course (I guess) that was "started" in the app. The end of the story is that he was able to put the app to Appstore but after a lot of rejecting. Once the Apple review team had understood that he was selling physical good they released the app.
I your case I think that IAP is the way to go.
Reading the point 11 of App store review guidelines will answer some questions.
We are an university department for further education courses and we are planning to publish our cd based courses as an additional iOS/Android App. As we have almost finished the development process we are now facing some questions regarding the distribution. The basic idea is to publish the app in a lite version for free (including chapter one of the course). After you have completed this chapter you will be asked to enter your login data. Our students will be able to enter thier data to activate (download missing content from our server) the app. If you are not an enrolled student there will be a link to our course page. On this page you can enroll for the courses and of course there is a charge for this.
But Apple only allows purchases via the App Store or as so called "in app buys".
Will we violate this rule with our idea?
I have found some newspaper apps with basically the same concept: download for free. If you have a print subscription for this newspaper you enter your data and can use the app. If not you can subscribe for the online offer via an in app buy.
After days of research we have no clear answer to this scenario.
Any comment appreciated.
There are two possible solution for your situation:
Without In-App Purchase: You can create an app which can have a eBook (in your case, dummy eBook with chapter 1 content) bundled with the App.
By doing this anyone who can download will have access to the dummy eBook as well.
For downloading of additional-contents user can do login and access the eBooks available with their account.
Kindly note as you are not using In-App purchase there shall be no links for user registration, buy inside your app.
All these you can handle at your web-site.
Your app can check for valid user credential using a web-service call, and user can see the contents available for download.
Advantages: 1) You shall not be paying 30 % to Apple as No-purchases are done using your app.
2) This is total compliance with Apple guidelines, this link and part 11 specially will be of interest.
Disadvantage: Users cannot directly buy/register via app and you need to maintain additional services for user login validation/content mapping/download content etc.
Using in-App Purchase:
You can use Apple provided in-App purchase for selling content/ registration of users etc.
Please note Apple shall charge 30 % on your selling price.
Advantages: Users can register and buy directly using your app. In-App purchase guidelines will help more in this.
Disadvantage: Apple will charge 30% on Selling price.
Given what you are trying to do, there really is no clear answer for your question that this community can provide, I'm afraid.
The true answer is entirely up to Apple's current app review policies. You should probably submit the app, explain clearly what you are doing, and if it gets rejected/denied, you can follow up with an appeal to the app review board.
As far as I know, physical items that are purchased are not subject to Apple's 30% cut. However, since you're offering courses / content over the 'net, Apple may want some percentage (between 0 & 30%) of the the profits you're making. Maybe they have a different arrangement with newspaper publishers. Ultimately, you'd need to submit the app and find out what the reviewers and app review board say.