Check out some of the questions, answered by Cheney Tsai (Sr. Solutions Engineer) and Philip Kreigal (Specialist Engineer) during Mobile UX Marathon livestream on Progressive Web Apps
Q. With PWA how do you ensure that the customers data is safe as it is in the native app store?
A. The common misconception is that the web is bit more insecure than the native apps. There are pros
and cons of both. Apps may say there are some protections but obviously if there are millions of apps, some things might not be able to get checked. The thing about native apps is that they cannot stay in box a lot of times. They exist in your device and they ask for a lot of permissions and things like that, so the risks are there. what's really cool about the web is that within the web sandbox every single tab kind of being constrained by design. You are exposing a lot of times, by default, less information about the user from a security model, than what natively installed applications might have. The risks are more because there isn't a governing body to say your UI is misleading. It's more about vulnerabilities than your own code, your implementations can trick a user into accidentally submitting something. That’s just isn't necessarily with the websites of container being insecure but with potentially like a different site trying to pretend you or your brand and getting users to sign it.
There are ways to mitigate that like the whole change to HTTPS the browser model to show that is a secure site or secure elements of authentication like third party sign methods. This takes away some of the burden of security from you.
Browsers these days on mobile and desktop they don't yell at you if you're using an unsecure website. It just tells you like this site is insecure. So, it's not only a bad look for your site but it also warns users that they might be on a malicious site. On mobile, the browser doesn't have access to necessarily to all the same API. At Google i/o we talked about what chrome is doing to kind of make sure data privacy is first and foremost for users. The browsers are pushing visits for opt-in and data's only share where necessary.
Q. Can you access the smartphone sensors from a PWA like camera location etc.? How does it work?
A. Yes. Anything that the browser can access, a PWA is able to access. In particularly notifications on Android devices you can get notifications from PWA. You can use PWA on desktop and get notifications there. Like News websites, it will tell you do you want to get news notifications from The Telegraph. That’s PWA. So, you can essentially access that on Android and desktop.
iOS is slightly more limited on they still haven't given service workers the ability to interact with the notification.
Q. How does the role of machine learning helping users personalize their experience come into play as an example of Progressive Web Application technology?
A. Machine learning isn't necessarily present on front end or designing your front end but if you do want to customize that user experience there's certainly stuff that you can be doing on the back end to pre-process and get ready on what you want to serve to that users based on what they've done in the past.
Question is what should exist on device and what can be done on the server. There haven’t been great examples about for typical website or typical app what do you use machine learning for. The common patterns are like we're going to predictably guess where you might go next or from a content standpoint search results which ones the users are more likely going to engage with, but this is stuff that arguably doesn't have to exist on the client. It would exist in your server code, processing your data ahead of time not on demand. There are exciting things like tensorflow j/s that allows for more creative uses of evaluating models on fly and in the web context.
It doesn't train the models on a phone as that would be computationally intensive but creates like new use cases like being able to recognize something the user is scanning, and it only happens on device.
We're talking about personalization and we're moving from a world pf passive personalization,
where the user doesn't really know that they're getting a personalized experience to active
personalization where the user knows the personalization and recognizes the information that you're using to give them the personalized experience. There are a lot of dynamics involved and
UX changes with regards to that.
Q. Do PWA cause any issues for SEO?
A. PWA is for websites. Whatever SEO you're using for websites, same techniques are relevant for PWA. Adding PWA does not suddenly change your SEO.
Q. Do PWAs replace mobile apps?
A. Take example of Spotify. PWA does not replace mobile app. It’s just a way to lead somebody in. Having PWA in emerging market is useful where data is expensive. So somebody might not be willing to go ahead and download a full application and so Spotify utilized that PWA to give them a little taster of what Spotify I like, what it sounds like and then once your are convinced you go ahead and make an investment into actually downloading the app. PWA, just like an app, it's a medium for delivering an
experience and depending on the conditions that a user is in one medium might work better than the other but it's not necessarily a you know one or the other kind of scenario.
Q. Can we expect a PWA to perform with similar speeds compared to a native app?
A. You can have extremely slow PWA and you can have a very fast PWA. We've seen PWA's were
know once launched full screen side by side next to native app and it feels just as fast. You'll find that
websites we've been optimizing for fast initial load (using lighthouse to run and measure your speed at fast initial look). Most websites boot up faster than most applications. So it’s mostly about interactions.
Q. What are somethings to be considered when choosing PWA?
A. Make sure that you're not abusing the extra capabilities that are given to you by the PWA. There are a lot of design ideas that needs to be figured out about what makes the most sense and it goes into your design for your PWA. The other consideration is usually the time investment in building a progressive web app.
Listen to the full webinar here : https://www.youtube.com/watch?v=RxZhr3zLNdw
Комментарии