RCS User Experience Guidelines
The official version of the joyn Blackbird PDD is now available
The GSMA joyn Product Group has incorporated feedback from a wide range of companies into the final version of the Product Definition Document (PDD) for the next generation of joyn, code-named Blackbird. The PDD provides guidance to Original Equipment Manufacturers (OEM) and Application Developers on the implementation of the Blackbird (BB) release of joyn.
The joyn PDD Version 2.0 has completed the GSMA document approval process detailing what the User Experience should be when a Network supports Group Chat Store & Forward. Therefore changes were made to sections 4.2.5 (Group Messaging), section 6 (Group Chat) and section 7.2.1 (Group File Transfer).
joyn User Interface Brand Guidelines
The joyn user interface brand guidelines is to support the correct use of the joyn brand and joyn iconography in the context of the User Interface (UI) of devices in relation to the Blackbird RCS 5.1 Product Definition Document (PDD). The guidelines solely applies to a native joyn experience and does not apply to a downloadable specification.
Version 1.1 provides a correction to the two touch point tables featured on pages 5 and 18 for partially branded and branded experience which were mixed up and placed in the respective other chapters of the user guideline document.
joyn Blackbird Unicode Standard Emoji emoticons
This document sets out the set of required emoticons for joyn Blackbird as referenced by the joyn Blackbird Product Definition Document (see paragraph above). Download the document here.
V1.2 joyn Hot Fixes, User Experience Guidelines
The RCS joyn™ Hot Fixes, User Experience Guidelines document provides guidance to OEMs and client developers on best practices in presenting the features and functionality of RCS Version 1.2. This update of the document reacts to the evolution of user needs registered during the lifespan of RCS and is based on the experience gathered from the first RCS implementation. This version reflects the functionality defined in RCS UNI specification V1.2.2, the joyn Hot Fixes functionality defined in July 2012 and on joyn Hot Fixes – Additions to clarifications technical implementation RCS-e guidelines V3.3.
These guidelines have been revised to ensure a good design and pleasurable user experience by making some sections mandatory, and adding standard translations for some of the common joyn functions and notifications. Alignment with the guidelines will form part of IOT requirements for joyn clients. The guidelines reflect feedback from multiple operators’ field trials and focus groups and as such reflect best practice in presenting the features of joyn to customers. OEMs continue to retain the ability to create unique designs but with similarity across key features ensuring minimum customer disruption and maximum uptake.