Rules & Guidelines

Eligibility

Entries for one or both categories of the RCS DevChallenge are welcome and from as wide an audience of companies and individuals as possible. Typical companies and organisations who might consider entry would include but are not limited to Client Developers, Mobile Client Developers and Usability Experts, Individual Technologists, University Technology Departments and Mobile or Fixed Operator Product Development Departments, Social Networking Experts, Service Designers, Social or Anthropological Scientists or Messaging Experts.

Category 1: Best RCS Client

The ‘Best RCS Client’ award recognises the most useable RCS client as decided by the RCS DevChallenge panel of judges. There will be a separate award for Mobile Device clients (Category 1a) and PC clients (Category 1b).

The judging panel will be looking for a novel client application that will clearly be seen to enrich the social or business use of communications and offer a new and attractive opportunity for mobile and fixed line users to share their real-time experiences with a mixture of voice, text, and still or video images. Additionally, it has to demonstrate a genuine value-added dimension with the potential for commercial deployment.
Clients can be developed for one or more platforms such as Symbian, J2ME, OMTP Bondi, Windows Mobile, Android, Apple, PC or others. Platform choices must be indicated on your Entry & Registration form. Entrants are encouraged to diversify their entries with clients presented on more than one platform.

The judges will announce their choice of three shortlisted entries for Category 1a and Category 1b after judging on Day 2 of the RCS DevChallenge ‘Meet’. The winner for each category will be announced at the world's leading mobile communications event, the Mobile World Congress in Barcelona, Spain in February 2010.

Judging

Important note:The assessment of entries in order to generate a shortlist for the finals will be made at a live RCS DevChallenge ‘Meet’ event to be held at Telefónica’s HQ in Madrid, Spain, January 27th and 28th 2010. The location will be Europe. Companies and entrants should be prepared to attend this event at their own expense.

The judges will expect to assess the clients on a device(s) as chosen by the developer – computer simulations of mobile device clients will not be acceptable. Entrants should supply their client loaded in a suitable mobile device which has already been configured to work with the RCS Reference System (see the FAQ section for more details). There is no restriction as to the type or nature of mobile device chosen to demonstrate the client application. PC based clients may be demonstrated on any suitable PC.

Although entries will not be specifically tested for interoperability, it is expected that they will employ a significant amount of the RCS specifications. Judges will take the degree of compliance with the specifications into consideration when making their assessments.

Main judging criteria

The following is meant for guidance only. It is not an exhaustive list of criteria.

Usability

  • How easy is it for a consumer to use the Client?
  • To what degree is its use intuitive?
  • How obvious is it to navigate around and between the features?
  • How does it make good use of mobility?
  • How will the usability enhance value to the end user?

Design

  • How appealing is the client – visually and functionally?
  • How clear is the layout of information when the client is in use?
  • How well does it provide an enriched communication experience for the user
  • What features are incorporated that demonstrate innovative use of design?
  • Does it offer a 'Cool factor' or will appeal to a particular target audience?
  • What is innovative about the design?

Breadth of conformance to RCS specifications

  • How much of the RCS feature set (as specified in <RCS Release 1> and <RCS Release 2>) is included in the client’s functionality?

Category 2: Best RCS Innovation

The ‘Best RCS Innovation’ award recognises the most innovative, compelling and creative idea for an innovative extension to RCS that will drive interest in and use of RCS services by global consumers. The idea could be demonstrated by a ‘mash-up’ of RCS and one or more additional services as determined by the entrant. The winner will be decided by the RCS DevChallenge panel of judges having reviewed the entry and taken into account the supplementary information supplied to support the entry.
The assessment of the judges will focus on the following main criteria of Innovation & Creativity as well as the compulsion of the use case from a customer perspective.
The judging panel will be looking for a novel RCS extension that will clearly demonstrate a potential evolution path for continued RCS innovation.
Additionally, it has to demonstrate a genuine value-added dimension with the potential for commercial deployment.

In this category, it is expected that the entry will more of a demonstration than the finished solution, and may be a “proof of concept” that only partially implements the entrant’s idea. However, the judges will be more impressed by entries that are closest to reality!

The judges will shortlist three entries in this category during the RCS DevChallenge Meet, with one winner announced at the world's leading mobile communications event, the Mobile World Congress in Barcelona, Spain in February 2010.

Judging

Important note: The assessment of entries in order to generate a shortlist for the finals will be made at a live RCS DevChallenge event to be held in January 2010. The location will be Europe and entrants are expected to be able to attend this event at their own expense.

Main judging criteria

The following is meant for guidance only.  It is not an exhaustive list of criteria.

Innovation & Creativity

  • How innovative is this extension to RCS?
  • How creative have the developers been in their choice of user application area as an extension to RCS services? How does this map to mass-market, user interests?
  • How obvious would it be for consumers to use this extension?
  • How does it improve or enhance personal communications?
  • Does this innovation link RCS to other communities? If so, how does this benefit the consumer?

Compulsion of the use case from a customer perspective

  • How appealing is the service – visually and functionally?
  • How well does it provide an enriched communication experience for the user
  • Does it offer a 'Cool factor' or will appeal to a particular target audience?
  • Will the service be perceived as a service having a high commercial value
    by the end user?
  • Why should this extension be seen as relevant by the target audience?