ubuntu-phone team mailing list archive

[Davide Alberelli <dadexix86@xxxxxxxxx>]

@Alan
Well, the "bookmark" is my experience with webapps.
All the webapps that I daily use are nothing more than bookmarks (gmail,
dict, OSM, Amazon, tumblr, various games, ecc) and often the websites
themselves say that I should use the native app for Android instead of
going to the website ;)
All the other features that you are mentioning sound definitely
interesting, but none of them are useful to me now, nor I have seen them
yet anywhere in my daily experience.
So, why should I use a webapp instead of going to the website? The only
reason that I have in my daily experience is because it is a nice bookmark.

Davide Alberelli

2015-06-05 11:31 GMT+02:00 Alan Bell <alanbell@xxxxxxxxxx>:

>  I don't really think we should describe webapps like that, it just makes
> them sound like an amazingly long winded and awkward way of making a
> bookmark to a site. They can do so much more, they can re-theme a site to
> make it look more native (yeah, problems with that, I know, themes are
> broken), they can inject scripts to do different things, so a useful
> banking webapp could scrape stuff, so you select a line on your credit card
> statement and post it to an expenses form in your Odoo system for example.
> Presenting webapps as bookmarks is just their least interesting feature and
> generates masses of really quite pointless webapps.
>
> Alan.
>
>
> On 05/06/15 10:24, Davide Alberelli wrote:
>
> @Marco for some things I agree with you, no big deal. For example
> newspapers, blogs, ecc.
>
>  But for others I do not and I really see the difference. For example,
> the bank websites.
> The huge difference is in efficiency and precision.
>
> To navigate to the bank website you need to
> 1) open the browser (1 tap)
> 2) type the correct name of the website (10-20 characters + the high
> probability to tap it wrong on small keyboards like the phone ones) or look
> it up on some search provider
> 3) type username and password (usually other 30-40 characters)
> 4) provide double-checking identity (various ways, other tappings, maybe
> 10 characters)
>
>  total: about 60-70 taps
>
>  While with a webapp you should be able to do it in
> 1) open the webapp
> 2) provide username and password (30-40 characters - optional: the
> username and/or the password could be remembered, depending on the
> conditions provided by the website)
> 3) provide double-checking identity (10 characters)
>
>  total: about 40-50 taps (or even 10 if the website allows to remember
> username and password).
>
>  And the less you tap, the less you can make mistakes and mistypings, so
> having a webapp prevents you to make 20-60 mistakes.
>
>
>   Davide Alberelli
>
> 2015-06-05 11:09 GMT+02:00 Marco F <maic23@xxxxxxx>:
>
>>  > From: robert.park@xxxxxxxxxxxxx
>> >
>> > Thankfully, if the webapp isn't sending your password off somewhere,
>> > the app should be really trivial.
>>
>> So what is the point of having a webapp if you can just navigate with the
>> browser to the bank website? And the browser also shows you a 'lock-icon'
>> to indicate a secure connection, which the webapp does not? I don't really
>> get the point of installing a webapp for every website that exists...
>>
>> Marco
>>
>> --
>> Mailing list: https://launchpad.net/~ubuntu-phone
>> Post to     : ubuntu-phone@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~ubuntu-phone
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
>
>
>
> --
> Mailing list: https://launchpad.net/~ubuntu-phone
> Post to     : ubuntu-phone@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~ubuntu-phone
> More help   : https://help.launchpad.net/ListHelp
>
>