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 9 years ago.
Improve this question
Today's world is mostly converted to mobile platform from the desktp platform and most of the payment trasaction, purchase and ecommerce facilities available via mobile applicaitons.
So, What is the best way to do payment integration in mobile application specially in iPhone, iPad, Android, Blackberry and Windows platform? There are plenty of third party API available out there but which one is the secure method to do paymaent gateway for mobile application development.
(1) For iOS platform we have inApp Purchase but it takes almost 30% to the apple and owner will get only 70% of the payment. Still there are some limitations are there as we can't provide the physical goods and services via inApp Purchase.
(2) Paypal is the secure method of payment gateway and it is also implemented in many of the mobile applications.
(3) Direct credit card payment option is also great one to use.
(4) There are many third party APIs available out there.
So, Here for mobile application development which is the best method to use specially for iOS platform like iPhone and iPad application that can be easily approved by apple without any problem.
We have two APIs for payment integration with iOS apps. The first uses app to app integration where transaction data is sent from the developer's app to our payment app. The other API allows developers to seamlessly integrate our payment app functionality into their app. Both APIs allow for easy approval by Apple and removal of the PCI-DSS compliance burden. For more info you can start here: http://developers.moblized.com/.
Update: We'll have similar APIs for Android by April 15, 2012.
If you have in app purchases, they HAVE to use Apple's API or else your app will be rejected.
The only way to (sort of) get around it is to have the purchase be on a website and it will unlock something on your app. You can't link to the website from your app though so it's kind of useless if you don't already have users visiting your website. This is how the Kindle app does it since Apple forced the use of their in-app purchase API.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 7 years ago.
Improve this question
I'm building a simple iPhone app with my developer. The main purpose of the app is to simply open my site on its mobile browser. In my site there are two log in options:1. Login via Google and 2. log in via Facebook.
But when my developer went to register this on istore the app has been rejected.
Here is what I received from my developer:
"As per Apple’s guidelines the app should offer features which should provide some interaction with the iOS device like your website offer login using Facebook which should actually be using iOS’s own FB login. Further the website offers searching for contacts, so we can have something like saving those contacts on device memory.
However, all these changes will involve efforts which need planning and are also not small tweak which can be made today and resubmit the app. "
So he is asking me to include log in via FB using APPle SDK otherwise my app can not be submitted.
Can anybody help me to solve this issue?
Thanks
Apple's AppStore Review Guidelines include the following:
Apps that are not very useful, unique, are simply web sites bundled as
Apps, or do not provide any lasting entertainment value may be
rejected
As I understand it from your description, your app simply shows your website. You should think about some additional features that could be integrated. One that apple seems to have included in your rejection might be a "native login" using the Facebook SDK for iOS.
I want to integrate any third party In-App Sales credit systems in my small gaming application. In my application,there is some game levels. I want to give some levels of gaming as free, after some levels, user should be purchase levels. So, please suggest me which process is better for integrating third party credit payment systems in my gaming application with out using Apple default In-App purchase feature. Is it possible to do like this.
Thanks in advance.
Check the App Store Review Guidelines, section 11 (I won't reproduce it here). If you use anything other than Apple's in-app purchase API your app will be rejected. Even the biggest companies (e.g. Amazon) don't get around this rule. The only way you might get around it would be to handle all payments outside the app, such as on a website, and then link the app to the website. No guarantees that Apple wouldn't reject your app anyway though.
I got an offer to develop a simple iPhone app that would call a web service with user's credentials. An user would get the list of files that can be downloaded (.pdfs) and could then download the wanted file. Simple enough...
Now, I've had bad experience with publishing on AppStore. Basically, they refused one app because according to them our RSS reader for a online newspaper wasn't in accordance with their guidelines. They said that the application was a simple web aggregator which I won't argue now. Not now :)
So, back to the new app problem :)
I would like to know what are the options for distributing the new app. The client has a web page and wants to give it's visitor this app to get that data from their phones too.
Technically, the app doesn't have to be a native app. It can be a phoneGap solution too since it's quite simple regarding the functionality. Sincerely, I am afraid that there is no way that Apple will allow this app to be uploaded to their store being native, phoneGap...
P.S.
I would also like to know is there a way to distribute an "internal" (not publicly available) iPhone app? For example, a company needs an internal tool for their 500 employees, but can't afford to go through the process of conecting each device and compiling the app for each device individually...
If you want to sell customized apps to companies, you should consider the B2B program.
if you are in an enterprise that wants to deploy apps inside your company, the Enterprise Developer Program is a good choice.
For internal:
100 test devices.
alot of iphones with the distribution profile after the 100 devices
with the enterprise:
https://developer.apple.com/programs/ios/enterprise/
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 7 years ago.
Improve this question
I've developed an iPhone application that sends off emails which contain google maps, embedded using the Google Static Maps API. The app will be for sale on the iTunes store (ie not free).
Do I need to get a Google Maps Business account? If so, how do I even apply for an account?
A point in the right direction would be appreciated. I contacted google but got the default reply that created more questions that it answered. eg it said:
"Note:
a) The sale of a product with Google Maps integration requires a special approval and associated licence upgrade."
but it didn't say how to do any of this.
Any tips would be appreciated
As per Google:
Usage Limits
The Google Places API has the following query limits:
Users with an API key are allowed 1 000 requests per 24 hour period.
Users who have verified their identity through the APIs console are allowed 100 000 requests per 24 hour period. A credit card is required for verification, by enabling billing in the console. We ask for your credit card purely to validate your identity. Your card will not be charged for use of the Places API.
So all you need is to give your Credit Card information and pay nothing.
You are not allowed to use the free Google Maps API on the iPhone if the App is for Sale unless you use Android with Google's store. See 9.1.2 Exceptions: https://developers.google.com/maps/terms
(Free Access) does not apply if your Maps API Implementation is used in a mobile application that is sold for a fee through an online store and is downloadable to a mobile device that can access the online store.
A commercial Maps Api License is too expensive for most cases.
Note: This mostly affects Webviews, because the built in Mapkit on newer iOS serves Apple Maps, not Google Maps.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 5 years ago.
Improve this question
Our business is currently looking at developing iPhone versions of applications we build for our clients. The apps are currently used internally within these businesses and are not (currently) web-facing.
A stumbling block seems to be deployment - requiring all of our clients to sign up for the iPhone enterprise programme won't work, as this is a big ask for companies who outsource their IT infrastructure (e.g. this simple task will probably end up costing lots of time and money and become a project in itself!).
I've been doing some research and haven't found a straight answer so far - is Apple happy to distribute applications which require logins to existing (paid for, business) services? I guess my main examples in this case would be spotify (not business but requires paid account) or Salesforce.com (again, requires paid account).
While there are many examples of it being allowed (Spotify, Twitter and Facebook clients, etc.), here's one which Apple rejected for requiring registration:
http://readitlaterlist.com/blog/2010/08/version-2-2-rejected-new-rejection-reason-from-apple-may-have-major-implications/
However many people on Hacker News considered this to be a mistake on the reviewer's part, rather than something in Apple's guidelines:
http://news.ycombinator.com/item?id=1626034
Is Apple happy to distribute applications which require logins to existing (paid for, business) services?
Yes, there are very many examples:
Amazon.co.uk and all the other shopping apps might be examples
Streetcar
iDisk (by Apple)
Find My iPhone (by Apple)
Sky+
...
Sklivvz is right, the only gotcha is they will already need a login to your service. If you let them create and pay for an account inside the app, you will have to use Apple's in app purchase and Apple gets 30%.
cf App Review Guidelines, section 11 (Purchasing).
Alternatively, you can launch Mobile Safari from the App, and after registering you can pass their login details back to the app using a custom URL handler (eg. myappid://somestring/) here is an explanation of custom URL schemes http://www.idev101.com/code/Objective-C/custom_url_schemes.html