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 :)
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Questions asking for code must demonstrate a minimal understanding of the problem being solved. Include attempted solutions, why they didn't work, and the expected results. See also: Stack Overflow question checklist
Closed 9 years ago.
Improve this question
I always used to in-app virtual goods or subscriptions, but my client wants to sell real products as toy art. Someone could tell me how it works?
I sell real products through my application? How would I do this using in-app or pay pal? The apple approve.
Thanks
In app purchase is just for the content in the app, bonus levels, virtual coins and subscribes. Of course you can sell real world items in your app, Apple accepts this kind of app, but remember you can not use Apple's in app purchase to charge users. Your must turn to other payment method, like Paypal or credit card.
Because it is something related sensitivity data (for money, you know). So maybe you have to supply your own use term and assurance to make your users trust you.
If you plan to use Paypal to implement the payment, you might want to see the Paypal's iOS SDK.
Apple doesn't allow selling real-world products by in-app purchases.
Here you have guide from Apple. Check pages 3 and 6.
If it comes to the second part of the question, you can redirect a user to prepared site to finish transaction as long as it's not stuff for the app. More about this you can find here.
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.
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 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 12 years ago.
Improve this question
As we are developing an iPhone app for a customer and he wants to charge for that app, we are wondering if it is possible to have multiple bank accounts in iTunes connect to have the revenues directly on the customers bank account. Whats the best practise for that?
Many thanks in advance
Stefan
It sounds like you want to distribute the app yourself on the store, rather than having the customer do it. As someone who does this kind of work himself, I can tell you that this is just silliness. Your customer should be sending you the certificates for you to sign the app, you send him the app for submission, etc. Never put this up under your account, really.
EDIT: You should tell your customer that he needs his own developer account, then guide him through getting you the certificates you need.
You need to set up another developer account in that case.
I'm not sure if you mean multiple accounts for the customer to be charged at or multiple accounts for your developer to receive their payments at.
If it is the former that sounds impossible to me (your payment is through Apple as a mediator, you should have no knowledge of customer payment methods).
If it is the latter, couldn't you either a) make a different account per app or b) talk to Apple support about this as it is a billing question?
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.