http://www.jollaes.com/2015/03/mwc15-dia-2-other-half/
 
capteur infrarouge, tohkb by dirk himself and TOH OLED  
 
http://www.jollaes.com/2015/03/mwc15-dia-2-other-half/

We’re also working hard on the next Sailfish OS upgrade (called Äijänpäivänjärvi, try to pronounce that!), which is currently in the release candidate phase.
If everything goes according to the planned schedule it should be out in a few weeks.
This release will include e.g.
landscape mode for Maps,
Split keyboard in landscape mode with a setting to disable it,
IMAP idle/push support for mail accounts,
and resolution independent icons.

Hi all,
 
During the last iteration, we had an intensive development period on  
tablet hardware adaptation and the new UI framework. The results were  
demonstrated at Mobile World Congress early this month. We are  
overwhelmed with the positive response and reviews of the Tablet. Do  
take a look at the blog entry summarizing our participation at MWC if  
you haven't already: https://blog.jolla.com/mobile-world-congress-2015/
 
A quick recap on the progress so far:
New UI framework:
  * Lockscreen with time, day and date information
  * Media player controls in lock screen for native Media app
  * Persistent status area in homescreen and lockscreen
  * Richer eventsview with widgets such as
    - displaying weather info
    - upcoming calendar events
    - shortcuts to toggle commonly used settings such as bluetooth,  
airplane mode, wlan and location,
    - shortcuts to perform quick actions , e.g search on web, take a  
picture, make a note etc
    - improved notification handling, grouping, secondary actions
  * Power key menu
  * Carousel transition to access home, open apps and events view
  * New swipe animations and transitions
  * Presence settings moved from events view to settings app
 
Landscape mode and layout updates for apps for tablet:
* Work in progress for Settings, Startup wizard, Calculator, Media  
player, Calendar and Gallery apps
 
Drop upower in favour of statefs:
Implementation work is now complete, now working towards gracefully  
handling the removal of obsolete packages. This task depends updating  
Mer Core OS to use newer version of libsolv, libzypp, zypper libraries.
 
GStreamer update to 1.x:
* More work on cleaning up the code for gst-droid encoders and decoders.  
The code is now more robust.
* Viewfinder and captured images should have the correct orientation.
* Hunting down issues with writing the correct orientation for the  
recorded videos.
* Porting the thumbnailer to a more recent libav
* Making sure qtmultimedia can be used with GStreamer 1.x by building  
it, rebasing nemo patches on top of it and fixing any issues.
* PHONE ONLY: jolla camera more or less works with some issues  
remaining. Gallery video playback with some issues remaining.
 
Toolchain upgrade to gcc4.8:
Moved to a later OS upgrade to give us time to complete the  
implementation of BTRFS balancing operation before performing OS upgrade.
 
For this iteration, we have planned the following:
* Kernel update to latest linux-stable version 3.4.106 for Jolla Phone
* Tablet adaptation work
   - recovery mode/factory reset operation
   - device identifiers supporting tablet OS upgrade
* Preparations for Bluetooth certification qualification
* Security fixes for  gnutls vulnerabilities (CVE-2015-0282,  
CVE-2015-0294), libgcrypt vulnerabilities CVE-2014-3591, CVE-2015-0837  
and openssl vulnerability  notified in  
http://marc.info/?l=openssl-announ [...] 619582&w=2
* Implement parts of voicecall-manager for SIP and other VoIP protocols
* Finalize the new UI framework features demonstrated during MWC
* Tablet-optimized apps and landscape layouts
* Refresh visuals for Sailfish Silica components
* Virtual/HW keyboard opening policy
* Email Search
* Improve folders list in Mail app
* Continue with the following from last iteration
   - Camera adaptation work on Tablet
   - File system layout  implementation for Tablet
   - Android runtime support Tablet
   - Continue working on landscape modes for apps
   - Settings pane to display disk usage
   - Allow factory reset operation to reset the OS to the latest  
available public version instead of the age old factory image
   - Upgrade to Pulseaudio 6.0
   - Private browsing
   - SIP integration into accounts. test IM capabilities in messaging
 
The following tasks unfortunately did not progress during the last  
iteration, we hope to catch up on them now.
   - Review certification middleware code
   - USB tethering UI
   - Enable open VPN support on the OS
 
The next OS upgrade, version 1.1.4 (Aijänpäivänjärvi) is in the release  
candidate phase. Here are a few highlights on the release content:
     - Landscape mode for Maps
     - Split keyboard in landscape mode with a setting to disable it if  
needed under Settings > System > Text input
     - IMAP idle/push support for mail accounts
     - Resolution independent icons
 
In addition, Facebook account has been updated to use API version 2.2,  
which has unfortunately lead to extreme reduction in functionality, i.e  
no instant messaging nor contacts sync. Facebook has notified that the  
XMPP chat API will no longer be available after April 30, 2015  
https://developers.facebook.com/docs/chat.
 
We have now moved our codebase to use new API version, thus disabling  
Facebook instant messaging capability on SailfishOS. It also limits the  
contact synchronization to only provide contact info of people using the  
same app; in our case this would mean that one could obtain contacts  
only if his/her Facebook friends are also Jolla phone users. We agreed  
internally that such a limited contact sync is pretty much useless to  
our users and hence the contact sync has also be disabled. We have  
initiated talks with Facebook in an attempt to find a way forward.
 
Thats all for now,
bijjal

Sailfish OS 2.0 -  Design Insights

Sailfish OS is currently evolving to the next generation (‘Sailfish OS 2.0′) and there are many design related questions, which we are working on, like:  Why is the User Interface perceived as simpler than before? How can I close an app super quickly? How to access Events? Can I have two Cover actions?

There isn’t just one reason why the UI is perceived simpler while very appealing. Instead it’s a combination of at least the following items:

Navigation_ModelSimple mental model of core views

We rearranged the core views so that they form a simple, easy to memorize model. Your relevant content is right in the center, whether it’s your notifications, personalized quick actions, running apps or optional content from a partner. Functions affecting the overall device behavior are accessible from the top. From the bottom you can always access your pool of apps with a simple edge swipe .

Edge swipes are consistent and context independent

Each edge swipe has one function. Left and right edge swipe moves you back to ‘Home’, a bottom edge swipe brings up the ‘App Grid’ and a top edge swipe opens the ‘Top Menu’. Simple as that.

Evolving with you

You can tailor the experience according to your personal needs and wishes. The baseline is simple and easy already when you get hold of the UI for the first time. However when you advance you are able to unlock handy tricks, e.g. closing an app via a top edge swipe or direct access to Events from anywhere in the UI.

Subtle hints and clear feedback

Subtle hints combined with improved visual feedback teach you how to use the device while exploring it. The different nature of UI views, like the Top menu and App Grid, are introduced to you via different visual graphics and motion graphics. This all makes the UI more predictable.

‘Built-in forgiveness’

When using devices quickly or in a hectic environment you sometimes may e.g. miss defined technical threshold for edge swipes. To avoid slowing you down we predict your intent and provide the intended function or view.

Balanced layouts and meaningful motion graphics

We put a lot of attention into layouts, scaling factors for fonts and graphical elements so that they are rendered beautifully and balanced on lower as well as higher resolution displays. The applied animations are meaningful and always serve a purpose instead of just being eye candy.

Separated Lock Screen from Home

The combined Lock screen and Home with a status area in between seemed to be a neat idea. However, it made Home complex and difficult to maintain from the technical point of view. Furthermore it restricted us to offer you a competitive UX in case of an enabled device lock code. Therefore we separated the two views from each other.

The separation of the two views also required a re-design of the status area. Here we maintained the great solution enabling apps to use 100% of the screen estate as well as the possibility to peek from an app to see status info. However we eliminated the two different interactions on Lock and Home to access the full status area, as well as the vertical jump effect of Home after swiping an app away. This greatly calmed down the behavior and makes it easier to follow the app and its position in the Home view.

On the Lock screen you can now apply either a left or a right edge swipe to unlock the device and access Home; the same logic as you apply when navigating from an App to Home.

The location of notification icon(s) on the Lock screen are now linked to the related action. This means whenever there is a notification icon, then we offer you a handy shortcut directly to Events via a left edge swipe.

Laid back app covers on Home

Home can now feature as many app covers as you want, and there is no limit to 9 visible ones anymore. In addition, the App covers do not all shuffle around anymore after swiping one app away. This is achieved via a new logic for positioning the covers: newly opened apps will go the end of the grid, while already open apps will go back to the same location where they have been. This change makes the whole experience more laid back, it’s easier to memorize the location of a certain app cover, and thus makes multitasking even more powerful.

Reduced set of Cover actions

Cover actions are handy. They become even handier if you select actions frequently used, if they really shorten a task flow and also make the cover easier to identify. After critically reviewing our current set we had to admit that some actions did not fulfill our targets anymore. Therefore we removed some, without removing the support for two cover actions altogether because they are convenient for e.g. the music playing use case.

In order to avoid accidentally activated actions while swiping between Home, Events and the new ‘Partner space’ we altered the interaction of the cover action, from horizontal swipe towards a tap interaction. We liked the gesture support, but when reflecting this against to the project objective then we had to let it go.

The same OS means the same UI

What is important to remember is that when the Jolla Tablet is ready, we will have one Sailfish OS, which supports different HW architecture, different screen aspect ratios and resolutions. This means that we will run the same SW and the same user interface on both the Jolla tablet and the Jolla smartphone; except a few modifications due to the smaller screen size of course.

Highlights

• Split keyboard in landscape mode, with option to turn it off
• IMAP implementation now has support for idle/push
• Maps now supports landscape orientation
• Facebook API has been updated to 2.2, which unfortunately causes loss of features (chat or contacts sync, see the end of the roadmap email)
• Better swipe feedback
  

We’ve been working very hard all year to get the Jolla Tablet ready.
We have progressed very well in many areas, but as there are still many open items remaining, we are forced to postpone the delivery start of the Jolla Tablet.
New shipping target for Jolla Tablet: end of July 2015