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 am developing an app for a company. The company aims at introducing models from foreign to domestic and the company wants to display all the models it owns on ipad so that some other companys who may be interested in can browse these models.
But when I read the "App Store Review Guidelines", I am not sure whether this kind of app could be accepted:
2.12 Apps that are not very useful, are simply web sites bundled as apps, or do not provide any lasting entertainment value may be rejected.
I am afraid that this kind of app which is not for entertainment nor for normal customer will not be accepted. Can someone can give me some advice?
If the app if for a legit model agency I don't think there would be any problems being accepted to the AppStore.
To me however every red flag in the book is up given your short description here - I expect that the Apple reviewers will have the same knee-jerk reaction to what sound like a dicey operation.
You could make an HTML 5 based web-app instead targeted at iPhone and iPad. Working with an web-app you don't have to deal with the Apple review process.
Make sure that your client doesn't inadvertantly drag you in to any legal grey areas.
As a rule of thumb if you're making an application over a web app for iOS bets are that you aren't literally just adding the website wrapped up into the app. The guideline interpreted by me means that you should beware making an iOS app for something a web app or an iOS ready site would've sufficed doing. When you say you'd let companies browse through products it makes it sound like the user will have the ability to interact with products in an iOS native way which is why us developers make apps. I'm not sure where Apple was going with the entertainment value part though but I'm sure that doesn't apply to business apps anyways.
Related
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 9 years ago.
Improve this question
I will be making an iPhone app that will sell ebooks. we have a website version of this and we want to have mobile version also. So, my question is what is the best approach(approved by Apple) for this kind of model? In our website version, we do payment by paypal. In my understanding, selling digital goods via paypal that is integrated within the app is not allowed(correct me if I'm wrong). Also, we have like 5000+ books on the website, so adding all books in iTunes(if it can be done) is no cake work I think. :D So help me out guys, this is my first app that involves buying and paying. After a successful payment, this book can now be read from within the app. Thanks!
Your correct, Apple does not allow any payment method for in app content that circumvents the IAP model.
You have two real options. One is to use IAP (In app purchase). This will give users the best native experience and will allow you to use apples framework BUT there are two downsides:
- Apple takes a 30% cut of all IAP revenue
- There is a chance that patent trolls Lodsys will come after you for unauthorized use of IAP (its not actually unauthorized, but they will try and argue that it is and sue you for it, google 'IAP Lodsys' for more info)
The other option that gives you more control over the payment system and gives you full revenue it to allow users to purchase books for their app on your website (The way kindle works). Not the best experience for users, but definitely best for your wallets.
Unfortunately I am not aware of any other payment methods, would be interesting to hear of some if anyone has any.
Hope that helps :)
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
** Please don't migrate this to Apple - it won't be seen. Thanks.
I'm not sure of the legal implications of what I am trying to do, but here it goes.
There is a radio show that I love listening to. It comes on everyday and the podcasts are uploaded to a website so users can download and listen to them for free. The website isn't very navigable, however, and it's extremely hard to play the podcasts from my phone (and, therefore, my car).
I have a long commute and I would love it if I could either access these podcasts via some kind of iphone app or maybe even a mobile-friendly website. I am first trying to figure out which would be better (iphone app vs mobile friendly website) and how sketchy you think it would be for me to develop the app (or site) and then offer it to the radio show for them to upload their podcasts. Alternatively, if they didn't want it, I would just download the podcasts from the site and re-upload them to mine.
Please note I am not trying to make any money off this, I am only trying to make it easy for people like me (with long commutes) to enjoy this particular radio show without having to navigate the existing (dysfunctional) site- risking the lives of dogs, squirrels, and other drivers in the process.
If you create an iPhone app, you will have more control over the OS-specific things that you can do but it will be limited to only the Apple platform. If you create a mobile-friendly site, it will be accessible from any platform but it will be limited by what you can do with a browser. I would say the target audience is the issue. If your target is just you or you and your iPhone friends, do the app. However, if you want scale, do the web app since it will reach the Android and WinPhone7 markets as well.
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
Working for a digital agency, you get a lot of interesting requests! :)
I have a client who has asked a rather strange question:
Is it possible to submit the same app to the App Store under multiple, different accounts/identities?
So if you search for Company A in the App Store, you would get this app as a result, and if you also searched for Company B, you would also get this app as a result.
Thanks!
Read the AppStore Review Guidelines Apple recently published.
2.20 Developers "spamming" the App Store with many versions of similar apps will be removed from the iOS Developer Program
Additionally, I think it'd be wise to advise your client against such a move, as it will only cause fragmentation for the app. Apps have keywords, so perhaps you should focus there to increase search results. I think you'd run into some issues submitting the same app to the store under different developer accounts--not to mention that you have to have individual developer accounts to even attempt such submissions. It'd really be a headache.
Technically, yes. At least if you're using different App-IDs and sign it with the distribution certificate for the account you'd like to upload it under.
I do not know however if Apple checks for 100% identical code / apps while reviewing apps - if not, it would propably work, if no, propably not :)
Even if multiple developers could get the same app approved, they would still have to change the app ID and the app name, so the search results would not show the same app, but multiple similar apps, all with different reviews and ratings, the aggregate of which would all be far lower in the popularity rankings.
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 1 year ago.
Improve this question
I've created an app, that is self-explanatory. What is the etiquette in the iPhone world: do I still need to have an About button that explains what the app does, website, email, all that? Or is that unnecessary?
I wouldn't consider it necessary, but then again I would get a second opinion about your app being self-explanatory; you wrote it after all :) Seriously, I've found a lot of "obvious" UI and behavior I've written over the years to be not so, and it's helped to have opinions from others (especially those who don't use computers for day-to-day work) to bring more clarity.
But from an etiquette standpoint, I'd say no: in fact if your app truly is self-explanatory it'll just get in the way of what your app does, which is what consumers are after.
I think that you almost always need one, especially in a paid application. You want it to be as easy as possible for your users to get in contact with you for support (no need to make an upset user angrier by making them search for your contact info), because happy users leave good reviews, and support requests often help you to figure out what needs work in your app. Additionally, if you release a free app but you also have some paid apps for sale, I think the free apps need an about screen that will send your users to your page on the App Store; after all, you might as well get some free, non-invasive promotion when giving away something.
The only time you probably don't want to include an about screen is when you don't want to hear from users. If you're giving away a free app, and you don't want to deal with people having problems with it, then don't even bother with an about box. Or if you're Apple, since about boxes in their apps would be redundant.
I don't entirely agree with zoul here. I think that every app should include information about how to contact the developer and/or get support if it's needed. Yes, you can put this information in the App Store listing, but that makes it more difficult for your customer. I'd say yes, add the About view.
The etiquette in the iPhone world is to design sane applications. If your application does not need an About screen, don’t do it. Those who want support can always check out your application description in the App Store.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
I am going to develop on iPhone platform. Can some one make an explanation about how to do this? Here is some of my question?
If I want to publish my iPhone software (totally free, and will be free forever), do I have to register apple developer with $99?
If I don't pay for apple, where else can I get detail development information (such as API documentation, library references, etc)?
What are the steps to develop and publish my software by the official way if I want to spend as little money as I can?
If you want to publish in the app store, you have to pay the $99.
There are tons of tutorials, and several good books available.
See #1. You've got to pay the $99 to publish the official way (through the app store.)
All that said, there is the concept of ad-hoc deployment which lets you share a limited number of apps with other people. The limit is 100 phones, and the users will have to go through a much more complicated process to get the app installed. The real purpose for ad-hoc distribution is getting your app to people who can test it before you send it to the app store.
In my opinion, after you've bought the iPhone and the Mac you have to have to run XCode, $99 is a pretty small price to pay. You're probably paying that much every month to keep the phone.