For me, it makes sense, it's like a back on ebook.
It's not the same move than switching application: to switch application you swippe from borders, not from the middle of the screen.

Mihai Barbat a écrit :
Hi all,

The problem with swipe from the middle is that it's not a back! Right now it switches to another running application. Ah, and it's also slow, at least on my Flame.

On Wed, Oct 21, 2015 at 3:17 PM, eyome <[email protected]> wrote:
Hi all,

to honest, I am against to add a back button to the home bar: I would prefer a swippe from the middle to the right of the screen.

I feel this elegant and really comfortable, please, considere it. It avoids to add another button on the home bar (and I could still using "home bar plus" add-on and his "kill app" button...).


Sam Giles a écrit :
+1

It seems wrong to have to build navigation into web apps when the platform has more than adequate support for it.  As an app developer I dislike the idea of having to provide my own mechanism to 'go back' to the previous view. As a user it can be frustrating, each app implementing navigation in a subtly different way.

These ideas would definitely be good to try out in Alopex.

Sam

On Wed, Oct 21, 2015 at 1:51 PM, Wilson Page <[email protected]> wrote:
I'm in favour of this model so long as it doesn't intrude on app developer real-estate with extra chrome. >From the early visuals we've seen from Alopex it appeared that the back button would live in the footer bar with the home button, which seems like a good solution :)

It might be nice to have this button appear only when there is history state to navigate back to. Or perhaps when there is no history the button does something else, like closing the app/tab?

W I L S O N  P A G E

Front-end Developer
Firefox OS (Gaia)
London Office

Twitter: @wilsonpage
IRC: wilsonpage


On Wed, Oct 21, 2015 at 1:30 PM, Michael Henretty <[email protected]> wrote:
Hi Gaia folk,

In the early days of Firefox OS, we built all of Gaia as single-page apps. I wasn't around then but I imagine we did this for a number of reasons, with performance and responsiveness at the top of the list. As part of this, we encouraged app developers to implement navigation controls in their own apps and not rely on browser chrome functionality like "back" and "refresh". This totally made sense in the context of a single-page app, especially when you take into account that native apps on iOS and Android (albeit to a lesser extent) have to implement their own navigation as well.

But with more recent technologies like Service Workers, better caching APIs, pre-rendering, etc. (basically all the stuff that NGA takes advantage of), I think the web is shifting away from single-page apps as a performance workaround. And let's not forget that single-page apps often negate one of the webs biggest strengths: deep linking.

So I write this email today as sort of an opinion poll. Personally, I think it's time we bring back the browser chrome into Firefox OS apps. I think we should encourage developers to write URL-based apps, to not be afraid of browser chrome navigation, and therefore to build their Firefox OS app as a standard website + some experimental (or proprietary :/) APIs.

There has been some discussion around this with the work we are doing on Pinning the Web and Alopex. But I want to hear from the greater FxOS community too, especially those with app development experience. What do you think, should we bring the "back" button back?

-Michael

_______________________________________________
dev-fxos mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-fxos



_______________________________________________
dev-fxos mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-fxos


Envoyé depuis Firefox OS

_______________________________________________
dev-fxos mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-fxos


Envoyé depuis Firefox OS
_______________________________________________
dev-fxos mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-fxos

Reply via email to