I'm looking into supporting P2P payments for a mobile app, iOS as well as Android. I do not think the PayPal API has support for this, what would be the best way to achieve this?
I need a verification preferably of a payment made to another user.
PayPal absolutely supports this. You have a number of options. You can use their actual mobile SDK's or you can just build standard HTTP requests to the API end-point like usual.
When using Express Checkout or Adaptive Payments their system will automatically switch to using the mobile checkout experience when a mobile device is used. This way you can build your apps to run on mobile devices or regular computers (with jQuery Mobile, for example) and it would give the user the experience they expect.
Related
I am planning to use socket.io inside a hybrid mobile application packaged for a mobile device. Are there any limitations that I might encounter with browser adoption or anything of that sort? Will this sort of a set up work with all mobile devices when packaged and distributed?
Updated details
I am going to use it to write a chat application. If I do a basic chat application using socket.io and then package it using PhoneGap or Cordova/Ionic, would there be any issues with compatibility or can I expect all the features to work seamlessly?
I Want to use UBER Ride Requests via Deep Linking in my website which is in c# so if user can book his Ride. how can i check whether a mobile on which my site open have UBER app installed,My site is in angular and in c#,
You can use the universal link, as described in the documentation:
Both the Android and iOS Uber apps support universal deep links. When linking from a mobile website, use https://m.uber.com/ul instead of uber://. The operating system will automatically open the Uber app if it is installed or fall back to our mobile site, which will open the phone's app store when applicable.
Is there a significant advantage of creating a mobile app as opposed to a web application?
I pose this question from the following perspective, which is biased towards my lack of knowledge of the mobile phone architecture.
You can build a web application with pure javascript, css, and html.
You don't have to write different code for iOS, Android, etc.
The user simply goes to a url, and that's your app, served right there from the server.
I would like someone to highlight some of the advantages of writing specific code for a mobile web application.
What does a mobile app fundamentally have a significant advantage over a web application?
Mobile apps have some advantages:
Assets are packaged on the phone - you only need to load data from
the server, not your layout.
Users are familiar with the conventions of their chosen mobile OS,
which your app will follow.
Trends show users are spending more time in Apps than web on mobile
Can work offline (even if limited)
Mobile apps have access to native features like push notifications,
GPS, Camera, etc
There are also hybrid apps - which are web apps running in a native container. You may have heard of Cordova, which is a platform for acheiving this. You basically create your app as a web app, and it runs inside a native WebView - with this you can use a javascript API to access some native features, but you don't get many of the other benefits of a native app.
Easy to use
Use native mobile design
Don't take long time to load just load data and images but web load (data/images/css/js)
I am not very experienced with this topic, but these are some fundamentals of using mobile apps:
They are accessible offline. (but that is restrictable)
The assets of the downloaded app are stored on the phone itself, thus the main content loads much faster.
As stated before, they have access to the hardware of the device (GPS, camera, etc, sensors etc.)
You can store as much data on the device as you want (opposed to, let's say 5mb using the HTML5's Local Storage).
They have access to push notifications (such as in Android or iOS)
They can put all the powerful hardware of the phone to use.
I am installing Flurry into a Phonegap application so that I might collect better in app analytics. I've seen numerous cordova plugins allowing you to use Flurry's iPhone and Android SDKs with Phonegap
e.g. https://github.com/jfpsf/flurry-phonegap-plugin
However Flurry has released a Mobile Web SDK. I assume the Mobile Web SDK is easier to integrate with a phonegap application, however I'm concerned that it is not as full featured or ill suited for working with phonegap. Can anyone comment on which SDK should be used in this situation? Many thanks.
Posing the question to Flurry's support team I received the following reply:
"The Mobile Web SDK tracks devices on the basis of cookies. The native SDK's track it on the basis of device id.
Apart from that, the mobile web SDK doesn't provide metrics like carrier, device and OS metrics. The native SDK provides those.
Crash reporting is not supported on the Mobile Web SDK. The native iOS and Android SDK's provide that."
Ergo, the SDKs are not created equally. One should use the native SDKs whenever they have the opportunity.
Is it possible / feasible to develop social applications with Corona SDK? I am talking about applications like Path, or a more feature rich application like Facebook for iOS?
We are going to develop a mobile application but don't want to assign resources for both iOS and Android versions of the software.
Maybe I should give more information about our project.
Users will use device camera, location services and there will be lots of web service calls as expected.
You can access the the camera as well. See the media.show() API Call: http://docs.coronalabs.com/api/library/media/show.html
Your web service access will be using the network.request() API call.
It is possible. Though I'm not sure about device camera but you can use location services and you can also develop a client side in corona