Commit 38e3f1ae authored by blendergeek's avatar blendergeek
Browse files

copyedit much of the Design section

parent d3b1ce86
Pipeline #627 passed with stage
in 58 seconds
......@@ -95,7 +95,7 @@ Must Have Apps
Nice to Have Apps
*****************
**Chess** (`GNOME Chess <https://wiki.gnome.org/Apps/Chess>`_): What would be a modern smartphone without a game?
**Chess** (`GNOME Chess <https://wiki.gnome.org/Apps/Chess>`_): What would a modern smartphone be without a game?
**Weather** (`GNOME Weather <https://wiki.gnome.org/Apps/Weather>`_): Weather forecast for different locations.
......
......@@ -3,7 +3,7 @@
Symbiotic Apps
==============
Purism’s long-term goals have always been to make computers that are as convenient as they are respectful to the people that use them. The Librem products are an ethical platform and therefore should not be discriminating against anyone; instead, they are meant to be inclusive of all human beings. In other words, everyone should find in their Librem a convenient and secure platform for their daily usage, and therefore accessibility should also be an important part of our ethical design roadmap.
Purism’s long-term goals have always been to make computers that are as convenient as they are respectful to the people that use them. The Librem products are an ethical platform and therefore should not discriminate against anyone; instead, they are meant to be inclusive of all human beings. In other words, everyone should find in their Librem a convenient and secure platform for their daily usage, and therefore accessibility should also be an important part of our ethical design roadmap.
We are aware that the road is long and that the Librem 5 is a challenging project, so we need some design foundations that favor convenience as much as it can lighten the development effort to get there.
......@@ -11,7 +11,7 @@ We are aware that the road is long and that the Librem 5 is a challenging projec
Apps on existing platforms compete for your attention
*****************************************************
With today’s smartphones, you usually get a minimal set of functionalities out of the box and go through installing diverse applications for your different needs. Usually those applications are proprietary and are designed around their own unethical business model. Therefore, they compete against each other for your attention and have their own set of features to be used within the scope of the application only.
With today’s smartphones, you usually get a minimal set of functionalities out of the box and go through installing diverse applications for your different needs. Usually those applications are proprietary and are designed around their own unethical business model. Therefore, they compete against each other for your attention. Each app has its own set of features and these features can only be used within the same application.
This can lead to a lot of redundancy and confusion in terms of functionality. A particularly blatant case is communication applications, where we see each application handling their own contacts logic, their own locked down and isolated protocol, and where a ton of applications will implement the same things for the same purpose (making calls and sending messages), with the focus typically being the flashiest application to attract and retain the most users. Let’s illustrate how ridiculous this is, conceptually:
......@@ -43,7 +43,7 @@ The idea behind the PureOS design guidelines is to replace the concept of standa
* Don’t see applications as independent programs but as “features” that have a single purpose and that interact with each other.
* One “feature” application is guarantor of the security of the data flow going through it. Only make your “feature” application share data with “trusted” features or networks and in a secure way.
* Make a “feature” application focused on one single purpose (an email client is not an address book nor a calendar)
* Make a “feature” application focused on one single purpose (an email client is not an address book nor is it a calendar)
* Make your “feature” application rely on existing features (an email client should rely on the existing address book and the existing calendar “features”)
* Avoid redundancy. Don’t try to reinvent existing applications. Improve them instead.
* Setup your “feature” application by default. Make it work out of the box.
......
......@@ -3,10 +3,10 @@
Touch Guidelines
================
Purism Touch (PT) framework is new visual language for
touch screen devices that shares visual principles of Gnome
Desktop and reflects it to new context of mobile devices
running Free & Open Source Operating System PureOS.
Purism Touch (PT) framework is a new visual language for
touch screen devices that shares visual principles of the Gnome
Desktop and reflects it to the new context of mobile devices
running the Free/Libre & Open Source Operating System PureOS.
|pic1| |pic2|
......@@ -22,16 +22,17 @@ running Free & Open Source Operating System PureOS.
**Single hand gesture range**
Average thumb movement comfortable reach.
Majority of users prefer use one hand for
interacting with mobile apps and system
interface. The position of a action target with
The majority of users prefer to use one hand for
interacting with mobile apps and the system
interface. The position of an action target with
respect to the thumb radius impacts
performance and general experience of touch
performance and general experience of the touch
interface.
**Touch Target Area**
Regarding action targets like links, buttons,
sliders and other UI elements, comfortable
space would not be less than physical square
7x7 - 9x9mm and cozy space of 14x14mm.
For action targets such as links, buttons,
sliders and other UI elements, a comfortable
size would be not less than a physical square
7x7 - 9x9mm. A cozy space of closer to 14x14mm
would be preferable.
Howto
=====
There are UI elements in GTK+ that are touch friendly (and therefore
good to use on a phone while others are not (e.g. combo boxes).
There are some UI elements in GTK+ that are touch friendly
(and therefore good to use on a phone) while others are not
(e.g. combo boxes).
This page will gather how to make a non touch friendly parts of an app
to become touch friendly. Until then have a look at these touch
friendly applications as examples:
This page will explain how to make the currently non touch
friendly parts of an app more touch friendly. This page is
still a work in progress. Until more is written, please
take a look at these touch friendly applications as examples:
* `Photos <https://wiki.gnome.org/Apps/Photos>`_
* `Calendar <https://wiki.gnome.org/Apps/Calendar>`_
......@@ -13,4 +15,5 @@ friendly applications as examples:
* `Builder <https://wiki.gnome.org/Apps/Builder>`_
* `Recipes <https://wiki.gnome.org/Apps/Recipes>`_
UI elements usually good to be used for apps on the Librem5 as well.
Any touch friendly UI elements should be good for apps
on the Librem5.
......@@ -15,6 +15,6 @@ Then after the user slides up, they will see the dial pad with some text prompti
Once the screen is successfully unlocked, the user will be taken to the home screen which is a matrix of applications. Note that the current image contains redundant placeholder applications.
The user will open up an application that will be full screen with two additional interactive points: can slide down from the top or tap the bottom bar to return to the home application screen. The "Power off" screen is also displayed in this picture along with a mockup onscreen keyboard.
When the user taps an icon to open an application, it will open full screen. The screen will have two additional interactive points. The user can slide down from the top or tap the bottom bar to return to the home screen. The "Power off" screen is also displayed in this picture along with a mockup onscreen keyboard.
Finally, the rightmost image displays what an incoming phone call will look like.
Finally, the rightmost image displays what an incoming phone call will look like.
......@@ -9,7 +9,7 @@ Librem 5 Docs
*****
Intro
*****
Welcome to the Librem 5 documentation! This site contains instruction and examples to help you accomplish your goals with the Librem 5 dev kit and phone.
Welcome to the Librem 5 documentation! This site contains instructions and examples to help you accomplish your goals with the Librem 5 dev kit and phone.
.. toctree::
:titlesonly:
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment