While learning about TWAs, most of the google tutorials have given example of oyorooms.com for its OyoLite app in Playstore, Myntra.com ( Myntra lite ), NavbharathTimes
However, when I measured these sites on https://web.dev/measure/ or https://developers.google.com/speed/pagespeed/insights/, their respective scores were in the range of 20-40.
Google documentation talks about a score of 80+ for the PWA to be considered for playstore.
So, the question is whether this is a strict guidelines by Google?
My app's current score is 55, should I invest time to bring it to 80 or try publishing the app directly?
Currently, publishing an app to the Play Store is not blocked on Lighthouse checks and applications are not suspended due to Lighthouse scores.
It is, however, strongly recommended and it will help ensure the application gets good reviews from users and that it has a quality similar to apps on the store built with other technologies.
Related
I am writing to you for the first time. I would like to know if with the "webview" configuration (https://firebase.google.com/docs/analytics/android/webview), it's good for hybrid apps and if you can track the transactions carried out on the institutional site, more precisely the payment takes place on the site and not within the app and understand that users who have converted arrive from the app and not from other channels. Thank you in advance for your opinion.
Elisa
If I have both a native app and a progressive web app using web push notifications powered by service worker, is there a way to prevent a user from receiving duplicate notifications if they opt in to receiving notifications from the web site and also have the app installed?
In short - there is no easy way to do this today.
There is a discussion on Chrome here on this: https://code.google.com/p/chromium/issues/detail?id=402223
The last comment from October 2015:
For now the safest minimal solution is for sites to provide an easy
opt out mechanism (which we strongly recommend you do anyway!) so
users can turn off notifications from one platform
Another possible heuristic based solution is to take some measure for
which interface (web or native) the user most often uses (or most
recently used) and only send to that. Combined with grouping these
devices by rough screen size should give a pretty good approximation.
The issue is that if the user has two similar sized devices and uses
native on one and web on the other then notifications will only be
delivered to one, which is an edge case.
We've also been discussing building an API so sites can tell whether
their corresponding native app is installed to avoid this case, but
need to start discussing that with other browser vendors to see if
they'd be supportive.
I notice there is no detailed insight on my app on iTunesConnect like android insight GooglePlay.
Is there any way to track user detail on every user install my app? I need more distinct information like, iOS version, phone provider, phone type, etc across installed app like in Android insight? does Google Analytics could do this?
Thank you.
There are quite a lot of analytics providers around that cater for iOS. As you mentioned, Google Analytics (which is free) should do what you need. Mixpanel is a really nice provider, but is only free for a certain amount of data. I've also used Flurry in the past (also free), but I find their web interface to be quite clunky.
If you want to track sales and App Store reviews, I'd really recommend AppFigures. Great service (paid, but a low monthly cost and you can cancel whenever), which gives you great insight into who's downloading your apps.
I have just changed from iAd to AdMob for the ads program on my iOS App.
The thing is that I just hate Apple's statistics at iTunes Connect. I wonder if I can use AdMob's Analytics addon to track all sorts of information such as downloads, devices, etc.
Is there anyway to have an statistical system such as Google Play has?
Well it is little bit hidden... but I have found these two interesting links:
https://developers.google.com/analytics/devguides/collection/ios/v2/
https://developers.google.com/mobile-ads-sdk/docs/admob/conversion-tracking
Good information though.
iOS 9.3, Xcode 7.3
Google Analytics has lots of customization options as to what data is gathered. "You get out of it as much as you put in." I mean, you will need to spend time integrating the analytics correctly to track what you deem significant. Determining what is "significant" is hard. The recommended approach is to start small and branch out into more detail later as you acquire customers.
This is what you'd expect as advertised:
The App Overview report summarizes the most useful information from
all of the Mobile App Analytics reports. Individual Mobile App
Analytics reports are organized into different categories:
Real-Time: See user traffic as it happens on your app. Monitor users, top active screens, top locations, and more. You can use
Real-Time as an end to end debugging tool for your Google Analytics
SDK implementation.
Audience: Get to know the people using your app—where they are, how often and long they use an app, and what devices are popular with
your visitors.
Acquisition: Find out how often your app is downloaded and installed, and how successful certain marketing campaigns are in
attracting visitors.
Behavior: Track in detail the ways users interact with your app. Find out which screens are viewed in a typical visit, or set up Event
Tracking to analyze custom actions, like button clicks and video
plays. Technical exceptions and crashes are also included in this set
of reports.
Conversions: Know the real value of your app. Set up Goals and Ecommerce to track targeted objectives, like completed sign-ups and
product sales.
To anyone who is looking for info on Google Analytics with regard to AdMob, please see this introduction, play the video and tune out for 30 minutes or so, it is very helpful. The topics covered in this link are:
About Google Analytics in AdMob
Set up Google Analytics in AdMob
Analyze a new app in AdMob
Create an audience in AdMob
Stop analyzing an app in AdMob
Google Analytics in AdMob FAQ
Here is the link to how to integrate Google Analytics in an iOS app., Add Analytics to Your iOS App.
Hope this helps!
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.