Android: Switch for in-app webview (help, etc)

Created on 27 Feb 2017  ·  8Comments  ·  Source: nextcloud/android

There should be a switch that would force opening of URLs (help and other, custom URLs) inside an internal webview rather than opening a browser.

cc @jancborchardt @tobiasKaminsky @AndyScherzinger

enhancement green

Most helpful comment

The user (in our app) will (for now) just use default external browser (maybe we can improve on this later). For the customer, yes, we need to force it.

All 8 comments

That would be best, yes. As for links do you mean the ones that might come in via the main menu extension or clicking on any kind of URL file which might be in your Nextcloud storage since for the later I'd say we should still give the user the choice to decide if he/she wants to go for their favorite browser or open it in-app (because with other apps like linkedin and xing, the in-app browser is rather pissing me off since I can't use my bookmarking service or other plugin apps...).

I mean the following:

  • links inside the settings (see second point)
  • custom sidebar links (that come in via an app installed on the server)
  • custom storage link that goes below the quota bar

As for files that you have, I'd still prefer to let the user choose rather than an internal webview.

✔️ links inside the settings (see second point)
✔️ custom sidebar links (that come in via an app installed on the server)
✔️ custom storage link that goes below the quota bar

as for the last one, we do have links _below_ the quota bar?

As for files that you have, I'd still prefer to let the user choose rather than an internal webview.

👍 sweet!

It will be a customer specific link, we currently dont afaik.

Is it necessary to force this? If possible, I would use the "android way" and let the user decide between

  • open internal
  • chrome
  • firefox
    (whatever app is able to handle an URL)

This will be shown on the very first time an user clicks on an url.

Edit: ...and then there must be a way to change it. So...settings is right. But maybe as an enhancement for the user additionally show it in the above way?

The user (in our app) will (for now) just use default external browser (maybe we can improve on this later). For the customer, yes, we need to force it.

So, how about we do it »The Android Way« as @tobiasKaminsky described it in the normal app? And additionally there’s a branding option by which it can be forced to open all these links internally.

There should definitely be no settings switch called »open links in internal or external browser«. It’s something you decide the first time or on a case-by-case basis – as intended by Android.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

Bugsbane picture Bugsbane  ·  3Comments

ikke-t picture ikke-t  ·  3Comments

tobiasKaminsky picture tobiasKaminsky  ·  3Comments

JSoko picture JSoko  ·  3Comments

tobiasKaminsky picture tobiasKaminsky  ·  3Comments