Streamezzo S.A. - All rights reserved
Copyright 2001-2010
Best Practices
This article provides you a guided tour of the best practices for designing a Rich Media Application with Streamezzo Rich Media Solution. You will find here an overview of the key aspects to take care of when developing your own appealing rich media applications.
Here you will be introduced with general good practices and recommendations on the following design keys:
- Application content optimization, to minimize the transfer, computation and rendering delays
- Dataflow optimization, related to streaming and incremental updates
- Portability and Adaptation, related to device heterogeneousness (screen sizes, texts display…)
- Cache management on both client and server side
- Errors management on client-side
- Debugging (process, emulation, logs…)
This article provides a brief overview concerning Rich Media Application requirements definition, i.e. basic information that shall be taken into considering when specifying such application.
This articles provides an overview of all typical issues related to devices fragmentation, i.e. specificities that motivate adapting the Rich Media Application implementation so it properly supports all targeted devices. All points of interest mentioned here shall be taken into consideration while designing such application.
This article provides basic guidelines to obtain valid media assets for a Rich Media Application.
Its deals with images, video and audio assets optimization.
This article provides the basic guidelines in terms of Java coding within a Rich Media Streamezzo Page (RSP).
What is the definition checklist?
This checklist is based on the experience gained through the development of mobile applications and will evolve according to the development of future applications, it provides the most up-to-date patterns and practices.
Use this checklist as a tool to help you define the architecture and design of your applications, in order to reach good user experience.
What is the review checklist?
Based on the experience gained through the development of mobile applications and updated according to the development of future applications, this checklist provides the most up-to-date patterns and practices
Use this checklist as a tool to help you define the architecture and design of your applications in order to reach good user experience.
This article provides an overview of all debugging facilities provided by Streamezzo in order to test and optimize developed Rich Media Applications. All available tools and the type of issues they can help addressing are detailed here.
This tutorial explains how to take care of potential errors that may raise during a Rich Media Application usage.
One should always consider how the application should react to such errors in order to take the appropriate decision, either restoring the application in a relevant state or at least informing explicitely the end-user that something wrong happened.
This tutorial explains how using incremental update facilities provided by Streamezzo framework.
Relying on this key feature enables optimizing a Rich Media Application - and especially improving the user experience - by reusing extensively Rich Media content that is already available on the device and thus decreasing latency.
This tutorial explains how to save and restore contextual data, i.e. data that can stored from one scene and consulted from another.
Such data will also remain available from one application usage session to another, i.e. if the application is quitted then launched again, this data will still be available (its cleaning is explicit, i.e. only performed on demand).
Your application has more than one single scene? Then it is likely that you will have to deal with a "Back" or "Previous" button. Here are some guidelines about how we handle the Back management to browse within a rich media service.
It is usually convenient to have the ability to deploy the same rich media service in multiple countries.
One of the issues to deal with is then to be able to support multiple languages within the same application.
You may observe that some asian characters (or may be all of them) are badly displayed on your device once you have deployed your rich media application on it. The usual reason for this is that the system font that the application will use by default may not be appropriate to display such characters.
The first thing said when reading books on Java application is that developers "do not need to worry about memory usage".
It's said that:
- A Java developer don't have to write specific Java code for freeing used object like in C or C++ languages
- The JVM is responsible for the memory management
But most of the time, applications in production face some critical issues related to memory usage.