On Wed, Oct 21, 2015 at 7:45 AM, Tim Guan-tin Chien <[email protected]> wrote: > > I am for anything that is closer to the Web experience as we know it. I have > been saying that since the beginning of the project -- "market expectations" > and other reasons unknown to me force us to mock an app experience instead. > > For the past 10+ years the Web experiences means the following: > > 0. URLs > 1. Linear history navigable with chrome > 2. Tabs, and easily switching between tabs
Fully agree with this. I would definitely encourage people to look at the draft that Przemek showed. I think it's a big step in the right direction. I do think that we will have some challenges when bringing the web model to mobile though. For one, the screen realestate is small enough that tabs might not work as-is. Having a list of tabs at the top of the screen sounds like it would look ugly/annoying, and so we'll have to figure out a different UI for switching between tabs as well as seeing what tabs you have open. Second, on desktop it works quite well to get back to previous websites by using the awesomebar. I.e. by simply starting to type a URL and have the browser help with autocomplete. However typing is more of a pain on mobile, so we might need to find better ways. This is where features like "pin the web" and "recently visited websites" can help. Both of these areas will need lots of user research and testing. I absolutely think that we should start with the assumption that we should build something that looks and feels like desktop browsers. But mobile is different because of screensize, lack of hardware keyboard and other things. So we need to prototype and test early and often to make sure that we create a good experience. / Jonas _______________________________________________ dev-fxos mailing list [email protected] https://lists.mozilla.org/listinfo/dev-fxos
