I am using Google analytics for my Web application and iOS application.
iOS application is practically an equivalent of its Web counterpart (they have same views, same functionalities).
I would like to have a combined report analyzing usage of both iOS and Web app together.
That means sum of all pageviews, tracking user's actions...
Quantcast Measure is designed for cross platform (web and mobile app) audience measurement. It has both a web SDK and a mobile app SDK that allows to to combine your web and app audiences into one comprehensive report. Quantcast's profile of GoodReads is a good example of what it's cross platform reporting is about.
(Full Disclosure: I work at Quantcast)
Forget about your mobile application, just create a responsive design version of your web app.
You will still be able to determine what traffic comes from Mobile devices.
Related
I've been trying to see if it's possible to get information about app usage on IOS. For example, how much time a user spends on his/hers Facebook or Safari applications. How could one go about doing this within a react native application? Is it possible to do it with any framework?
No, it’s not possible. Apple is very strict about this.
An app cannot access other apps' sandboxes, for any reason. Everything an app can do is restricted to its own sandbox, and in no way can other sandboxes be accessed.
User security is very important for Apple.
If the app you are trying to get the data about has an SDK that can be integrated in your react native app, and the SDK has APIs to provide information about usage analytics for the user(which I don't think is possible with FB SDK), you could ask the user for authorization via the SDK and show them the usage analytics information. Although, chances of these APIs being in an SDK are slim, this might be the only way.
What is the difference between SAP Fiori and Movilizer?
They both are used to show SAP data in mobile phone, then where is the difference?
Fiori- Rich UI design which have a capability to adopt all the platform and have an easy way to develop complex sap business logic
Movilizer-A product from Honeywell, which have an offline and cloud integration to collect data from enterprise (SAP, MS, Oracle) to Mobile app
Regards,
Karthik A
The way I understood it:
Fiori: web based apps
Mobilizer: Hybrid apps
Best regards
Not sure if you are still looking for an answer but:
SAP Fiori: A collection of applications written using the SAPUI5
framework and Fiori x.0 guidelines. Applications can be
containerized for use on mobile devices in addition to browsers. (Link)
SAP Mobilizer: A Java-based platform with applications for Banking,
Mobile Money, Wallet etc. The platform provides a mobile enabled app for mobile money, wallet, account management etc. alongside a customer portal.
Honeywell Movilizer: A field - orchestration product for managing
equipment. I'm not sure of their mobile offerings. (Link)
You might also want to look up SAP Mobile Platform 3.x (Link)
Hope that helps.
In ASP.NET MVC application how can I detect whether the user is using the Tablet device or the Mobile device?
Please I am looking for a no media queries solution.
There is nothing built-in for ASP.Net (you can test Request.UserAgent, but you need to know more info about specific device), you could detect the device client-side(with the help of something like web.wurfl.io) then parametrize your controllers, otherwise, if you are looking for a pure server-side solution, you could try WURFL => Wireless Universal Resource FiLe
WURFL is a Device Description Repository (DDR), i.e. a framework that
enables applications to map HTTP requests to a description of the
capability of the mobile device that requests the page. In this
regard, WURFL pre-dates the time when the DDR term was coined and
could arguably be caracterized as the first DDR. In the last year,
WURFL role has expended from being a DDR for mobile devices to being a
framework to detect every HTTP client worth recognizing.
Thanks to WURFL, mobile web sites and application can:
programmatically abstract away devices differences
avoid the need to modify applications whenever a new device ships
avoid the need to track new devices on the market
WURFL is a global database of all devices and the API to tap that
information programmatically.
We have a commercial web application and we are planning to develop android and iOS apps(free) for our customers
Is google maps ios sdk is free to use in my app?
we want to open google maps app from our app using custom url scheme to show driving directions. Does this approach have any restrictions?
There is nice FAQ about your questions on Google Developers website:
Is google maps iOS SDK free to use in my app?
Yes
we want to open google maps app from our app using custom url scheme to show driving directions. Does this approach have any restrictions?
Google Map API for Business - Usage Limits
The google maps iOS sdk is free for use. i have already integrated google map api functionality on one of my phonegap application. After making some minor changes in to the sdk you can enable the real time navigation on the google map as well.
so you can do a lot with the google sdk.
Hope this will help.
It actually depends, if you are using advanced feature eg Street View, it charges, but for basic feature, it is free for native app, but JS query is not free (eg wrapped by Webview) is not free.
Checkout the official website for more detail and accrete information: https://developers.google.com/maps/documentation/ios-sdk/usage-and-billing
I'm currently graduating at a small company which makes and sells accounting software.
My task during my graduation is to make a Mobile application which supports some functionality of this software.
For instance: making a report on site and uploading it to the server,logging hours worked, retrieving sales information etc..
I'm currently doing research on which platform I should deploy but I'm getting confused in what shape my application should be made.
I can't make a choice what I should recommend, Web app or Native app?
I need help making a recommendation:
Security is important. (we deal with confidential information)
Maintenance is very important. (they will have to support it in the future and have low resources available. (small company))
Development costs (I have no clue here.)
User experience (Because this is a business app, is a web app good enough?)
The business market here is currently very iOS (Apple) saturated (about 80%) but I do need to think of the future. (Android, WP7)
So What do u recommend with the given information, web or native? Do I need more information before making a decision / recommendation if so, what sort of information?
ps I think this question belongs on stackoverflow, if not please move it to the appropriate site.
For what you're looking to accomplish, I'd recommend taking the mobile web app route. Here's why:
Security is important. (we deal with confidential information)
You could make a case either way, but I feel that a mobile web app is better for security. Like Ganzolo said, it can have as much security as a typical web app. Also, since it doesn't store data on the device itself, you won't have to worry about a data breach in the event of a lost or stolen phone (assuming you're not using HTML5 offline storage).
Maintenance is very important. (they will have to support it in the future and have low resources available. (small company))
Mobile web apps have an advantage here. If you built native apps, you'd have to build and maintain separate apps for each platform. On the other hand, since one mobile web app reaches all platforms, you'd only ever have to maintain one app. Also, you won't have to update a mobile web app with each OS update, like you would with a native app. If you want to go one step further, you could even build a mobile web app with separate presentation layers for smartphones, tablet, and PCs (like this). That way, one mobile app would look different (yet native) on any device, but you'd only have to maintain one underlying application.
Development costs (I have no clue here.)
Depends on how many platforms you want to reach. If you're building for one platform, the costs are similar. If you're building for multiple platforms, mobile web apps are far cheaper. One mobile web app reaches all platforms, whereas you'd have to build a separate native app for each platform.
User experience (Because this is a business app, is a web app good enough?)
You'll get a better UI with a native app, but a mobile web app should be more than sufficient for most business apps. Use a good mobile framework (like jQuery Mobile), and you can build a mobile web app that looks and feels almost native.
The business market here is currently very iOS (Apple) saturated (about 80%) but I do need to think of the future. (Android, WP7)
Mobile web apps are a much safer choice for the future. Who knows what the mobile platform landscape will look like in 2 or 3 years? Maybe WP7 will be popular. Maybe some new OS will be popular. It changes so fast, there's no way to know. The only thing I do know is this: The web will still be popular. If you build a mobile web app, you insulate yourself from all future mobile OS battles.
I hope that helps.
My personal opinion would be to go for a web App :
• Security is important. (we deal with confidential information)
Sercurity in a web app cannot be worse than security in a regular website (like online banking)
• Maintenance is very important. (they will have to support it in the
future and have low resources available. (small company))
Maintenance is really easy for a web app since you can make updates without going through the process of submitting your app to the store and waiting.
• Development costs (I have no clue here.)
Development cost will be lower with a web app as you'll have 1 code for every phones (and most of them are using webkit which will be simplier)
• User experience (Because this is a business app, is a web app good
enough?)
It's hard to answer this question without knowing your project but for simple UI it can be good enough
• The business market here is currently very iOS (Apple) saturated
(about 80%) but I do need to think of the future. (Android, WP7)
Yes you need to think about the future that the most important because you can only do simple functionality in web apps. So if future requirement, will have more complex functionality then you'll have to move into native apps.
Hope I've been helpful
In my experience, web apps always tend to be sluggish on the UI front. I would always opt for a native app, if you don't have to support multiple platforms at once (iOS, Android, generic).
Security: Make your app connections over SSL
Maintenance: The only problem here is that you may have to wait 7 days for App Store approval for native apps
Development costs: Depends on who makes the app, shouldn't be too different.
UX: Defenitely native!
Multiplatform: As I said, for multi platform a web app is probably best
If you opt for a web app, make sure the user doesn't have the impression of "the app isn't doing anything" while loading stuff.