[Librem-5-dev] Application design principles

rinigus rinigus.git at gmail.com
Tue Nov 20 12:14:45 PST 2018

Hi Tobias,

I somehow missed that navigation gestures scheme. I would like to suggest
also a forward swipe for accepting a dialog action, similar to swiping
back. Its very well used on Sailfish and would fit with the other used
gestures, as far as I can see.

I agree with targeting main interaction pattern first and not worrying too
much about very fine details when matching the platform. Thank you for the
links, will look into it. But first, I'll focus on other aspects of
interaction with the user.



On Tue, Nov 20, 2018 at 2:29 AM Tobias Bernard <tobias.bernard at puri.sm>

> Hi Rinigus,
> We do want a swipe gesture for going back in pages stacks in addition to
> the button in the top left, it just hasn't been implemented on the GTK side
> yet. For a bit more detail see
> https://gitlab.gnome.org/Teams/Design/os-mockups/blob/master/mobile-shell/mobile-shell-gestures.png
> As for general design guidance (patterns, visuals, spacing, typography,
> etc.), have a look at the GNOME HIG
> https://developer.gnome.org/hig/stable/
> In GTK you get a lot of this for free, probably similar to the Sailfish
> style classes you mention, but of course it's more work if you use a
> different toolkit. That said, I would not worry too much about making your
> app look exactly like a GNOME app at this point. If it works well and
> behaves in ways that are expected to someone who is used to GNOME patterns,
> it's not that important that the spacing or typography is a little bit
> different in some places.
> As for your concerns:
> - We have discussed patterns for hiding the top bar in certain situation,
> eg. when scrolling in a browser or in video players. IIRC it hasn't been
> done yet because it would require a lot of work in GTK to make it easily
> doable for app developers.
> - Agreed, which is why we want a back gesture, it's just not implemented
> yet :)
> Cheers,
> Tobias
> On 11/16/2018 01:26 PM, rinigus via Librem-5-dev wrote:
> Hi,
> I would like to ask about main application design principles that are
> envisioned for L5. In particular, applications that are not using Gtk/Gnome
> libs and if they wish to follow the same or similar user interaction as the
> targeted platform. My questions and understanding of current design are
> based on
> *
> https://gitlab.gnome.org/Teams/Design/os-mockups/blob/master/app-menu/patterns.png
> * https://developer.puri.sm/Apps/GNOME/Gtk+.html
> * https://developer.puri.sm/Apps/Constraints.html
> * https://developer.puri.sm/Design/Design_guidelines/Touch.html
> It looks to me that the current guidelines imply:
> [1] user will be able to swipe up from the bottom to get main menu with
> all applications
> [2] application has some kind of a top bar with its name and menu symbols
> [3] to get back from the application sub-page, there is an arrow that can
> be clicked on the left top
> There are no indications regarding swipes as a part of interaction within
> applications. Namely, is it envisioned that we can make "page stacks" and,
> instead of reaching top left corner to go back, can swipe the page out of
> the stack?
> As an application developer, I am looking for some kind of guidelines or
> will be happy to help through the discussion and other means in formulating
> them. While not fully open-source, I would suggest to look into design
> guidelines of SailfishOS, which are quite clearly (for me) defined at
> https://sailfishos.org/design/navigation/ . In addition, on SFOS, we have
> rather extensive specification of used theme colors, distances between
> labels, font sizes, and such. For that, we use a dedicated QML class
> https://sailfishos.org/develop/docs/silica/qml-sailfishsilica-sailfish-silica-theme.html
> . Would be great to get some kind of similar resource that can be queued
> for application design.
> (Assuming that I understand the principles correctly) As for implied
> design principles [2] and [3], I have few concerns
> * having a top bar with application name is a large waste of space, at
> least for some of the applications. For example, web browser would not need
> it and its probably the best to have as much screen for reading as
> possible. For maps, same applies - the content speaks for itself in many
> cases.
> * having an arrow on top left as an only way to move back from the
> sub-page back, contradicts easily reachable thumb range (
> https://developer.puri.sm/_images/p2f1.png)
> Best wishes,
> Rinigus
> _______________________________________________
> Librem-5-dev mailing listLibrem-5-dev at lists.community.puri.smhttps://lists.community.puri.sm/listinfo/librem-5-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.community.puri.sm/pipermail/librem-5-dev/attachments/20181120/80c654b9/attachment.html>

More information about the Librem-5-dev mailing list