For in-app purchases that affects the iPhone app itself, it'll definitely be rejected as Apple would force you to use their in-app purchase API.
But what if the app complements a web service that I'm building that isn't only made for iOS.
It would seem weird that subscribers would have to go through two separate gateways for payment.
In other words, how does a web service passes app store approval for an iPhone version of the web app?
Noone currently knows for sure. Steve Jobs has said that the subscription rules were meant "for publishing apps only, not SaaS apps": http://www.businessinsider.com/steve-jobs-email-subscriptions-2011-2 But the guidelines are kind of vague.
Related
According to my application requirement, I need to integrate the Sagepay ios SDK, but on the Sagepay website, they don't provide any official document or flow also.
I try and get some code in the objective-c mode in here
https://github.com/ColorsSoftwarePvtLtd/SagePay-iOS
Please refer to me any SDK example codes in Swift or already existing links.
That looks like a third party project I reckon that's not an official SagePay supported SDK.
If app integration is extremely important to you, don't use SagePay and instead use modern providers like Stripe/Braintree/Adyen who generally provide SDKs and have better documentation / examples.
The support for mobile payments from SagePay is painful. We asked them for a ApplePay / GooglePay integration back in 2017 and they said then that they "are working on it". We've since gone with a different provider for those types of payments, and we're quite glad we did otherwise we'd still be waiting 2.5 years later.
At the moment for classic card payments we submit payment details to SagePay and then go to a WebView for 3-D Secure, which we've had to manage in our apps. There is unfortunately no nice SDK to use. For iOS there is this https://github.com/brightec/3DSecureView which helps somewhat with that.
HTH.
i am trying to use ucwa apis to get the users presence status. but I am getting issue as failed to get application resource
You might want to look at this discussion which discusses how to perform UCWA Autodiscovery for Skype for Business Online and get the application URL.
Presence has recently become available in preview for UCWA-powered SFB Online apps.
I've created a C#-based example that you can use as a basis in your UWP app, which includes changing presence for a user.
I wish to make chat application that will use background service that will persistently query certain server of clients choice.
This app is chat application.
I am developer of iOS application but I do not own/control these servers.
I can't share my APNS certificate with 3rd parties that control these servers.
So the only way I see to implement it on iOS is to use MultiTasking API and NSURLSession class.
Is it permitted create chat applications that will not use APNS but will use MultiTasking API?
take a look at https://github.com/robbiehanson/XMPPFramework. Just declare your app as a voip.
I'm architecting a public web API for my service. It will be equally consumed by web pages and native mobile apps (iOS, Android and Windows 8).
Should I use cookie-based authentication? I mean, is this the best practice for this scenario?
Futher Info:
After a little research in the authentication/authorization/openId-connect field i realized that most of everything is handled by the browser, by that i mean, the redirects, coockie insertion and related "boiler-plate" stuff... when i think about all that boiler-plate that i will have to duplicate in my natives apps, i wonder if that model is the best for mobile apps. i mean, maybe theres another more mobile-native-friendly way...
Ps: i know that this is a little generic still, it's just that i'm a begginer in the field of security and i dont know how to properly express my doubts/concerns/"laziness" still...
The API itself should really be stateless, and not manage any sessions. Each request to an API should be made with the authentication details (e.g. OAuth token).
If the Web pages and mobile applications need to maintain some kind of session, then it should be up to them as clients of the service to maintain that state. For instance, a Web page might set a session cookie for the user, but a native mobile app might want a completely different approach.
See also: If REST applications are supposed to be stateless, how do you manage sessions?
Are there any initiatives to implement/agree upon a standard API for connectivity between web browsers and client hardware.
Example: The iPhone has a GPS/Camera/Accellerometer in it. It'd be very cool if my web app could communicate with them (rather than me having to write a thick ObjectiveC application).
The closest thing I've seen to that is the Android phone API, which lets your programs access its hardware (relatively) painlessly. Google's pushing for it to become the new standard, but its hardly the same thing as a web-app (which, by most definitions, runs entirely in your browser?).
The upcoming version of FireFox has an API to read your lat/long off a GPS device.
To add to my own question; Yahoo provides a geolocation service called FireEagle that could act as a mediator and provide similar functionality.
In essence the phone communicates with a central Yahoo server updating its location. Your web app can then determine your approx location from that central server.