I’m writing this as a short commentary on Stuart Langridge’s post The Importance of URLs which you should read (he’s surprisingly clever, although he looks like the antichrist in that lewd hat).
I approve of the Lighthouse team’s idea that you don’t qualify as an add-to-home-screen-able app if you want a URL bar
Opera’s implementation of Progressive Web Apps differs from Chrome’s here (we only take the content layer of Chromium; we implement all the UI ourselves, precisely so we can do our own thing). Regardless of whether the developer has chosen
display: standalone or
display: fullscreen in order to hide the URL bar, Opera will display it if the app is served over HTTP because we think that the user should know exactly where she is if the app is served over an insecure connection. Similarly, if the user follows a link from your app that goes outside its domain, Opera spawns a new tab and forces
display: browser so the URL bar is shown.
But I take Jeremy Keith’s point:
I want people to be able to copy URLs. I want people to be able to hack URLs. I’m not ashamed of my URLs …I’m downright proud.
One of the superpowers of the Web is URLs, and fullscreen progressive web apps hide them (deliberately). After our last PWA meeting with the Chrome team in early February, I was talking about just this with Andreas Bovens, the PM for Opera for Android. We mused about some mechanism (a new gesture?) that would allow the user to see and copy (if they want) the URL of the current page. I’ve already heard of examples when developers are making their own “share this” buttons — and devs re-implementing browser functionality is often a klaxon signalling something is missing from the platform.
When I mentioned our musings on Twitter this morning, Alex Russell said “we’ve been discussing the same.” It is, as Chrome chappie Owen Campbell-Moore said “a difficult UX problem indeed”, which is one reason that Andreas and I parked our discussion. One of Andreas’ ideas is long press on the current page, and then get an option to copy/share the URL of the page you’re currently viewing (this means that a long press is not available as an action for site owners to use on their sites. Probably not a big deal?)
What do you think? How can we best allow the user to see the current URL in a discoverable way?
Here’s the keynote talk I did at Render Conference, Oxford in April. (Slides.)
All the other talks are available. Yay!
I told the nice organising types that I wouldn’t accept the speaker fee because public speaking is my job. Rather than just pocket the money, they suggested we donate it to a worthy cause, which is very good of them.
So I asked them to send it to a rural school in Cambodia, where a friend of mine has been volunteering. They’re building a computer lab to train kids and the local people. In one of the poorest countries on earth (average salary is $80/ month) a second hand laptop at $250 is still a luxury. As someone who was a primary teacher in Bangkok, this ticks all my personal boxes: education, S.E. Asia and the web.
Thank you, Ruth and all at Render Conference.
At the Google Progressive Web Apps afterparty last night, I had two very different conversations within five minutes of each other.
Conversation #1 went
Hey Bruce, lucky you weren’t at REDACTED conference last week. They were bad mouthing Opera! One speaker said, “Anyway, who cares about Opera Mini?”
In the time it took to drink another 5 bottles of free beer (two minutes), conversation #2 happened:
Oh Bruce, hi. We’ve just raised £100million in funding for our business in Asia, and 35% of our users are on Opera Mini.
What’s the difference? Well, for a start, one was apparently said by a European designer to a room full of European designers, in Europe. The second is the word “users”: the second conversation focussed on the fact that a technology is used by human beings, which is always, always the point.
Now, I don’t care about Opera Mini per se (I’m not its Product Manager). In the same way, I don’t care about walking sticks, wheelchairs, mobility scooters or guide dogs. But I care deeply about people who use enabling technologies — and Opera Mini is an enabling technology. It allows people on feature phones, low-powered smartphones, people in low-bandwidth areas, people with very small data plans, people who are roaming (you?) to connect to the web.
I ran the stats today. Of more than 250 million Opera Mini users, 50% are on Android/iOS and 50% are on feature phones. The second group almost certainly have no choice in which browser to use to get a full web experience. That’s 125 million people that designer-on-stage doesn’t care about. People like Donald from Nigeria, people like Silma from Bangladesh. People.
The top territories for Opera Mini use are India, Indonesia, Nigeria, Bangladesh and South Africa. Because conversation #2 was about tangible stuff – millions of pounds, and numbers, let’s look at the economic growth of these nations full of interlopers to our WWW (Wealthy Western Web).
(PPP= Gross Domestic Product per Capita, figures from CIA World Fact Book)
Sure, those PPP numbers might be low compared with the home countries of designer-on-a-stage and audience, but how do the growth rates compare? These are dynamic, emerging markets. Who cared about China ten years ago?
If you don’t care about Opera Mini users in these areas, you can bet your competitors soon will.