| Mobility |
Developments in mobile environments have been a pillar of Kynetia’s work for years. For example, it was Kynetia, through our spin-off Atinco, that enabled Telefónica Móviles to launch its first GRPRS video streaming service in 2003 and later to follow up with a UMTS service. If this mobile development commanded the greatest media impact, it is by no means our only achievement. In 2001 we had already developed the first online broker for use on Nokia Communicator handsets, permitting real time share transactions in the Spanish stock market. Another more recent example is Emminens (an affiliate of Roche Diagnostics), which utilizes software developed by Kynetia to integrate the blood-sugar measurement devices used by diabetics with patients’ mobile phones and with medical personnel in hospitals. At Kynetia we see mobility projects as being, in reality, an extension of the user/customer communication channel. In this light, it is necessary to pay close attention to the two key aspects of any mobility project, which are the client and the server. Client-side mobilityThe key success factor for any mobile telephone application is usability. It must always be remembered that the capacity for interaction between users and their mobile handsets are very limited, and applications should therefore always be designed in view of the restrictions experienced. The very diversity of mobile handsets is a further problem, which is closely associated with the diversity of user interactions with the device. For example, the user of an iPhone interacts with the applications it contains in a very different way to the user of a Nokia. Likewise, using a Nokia is not the same as using a Motorola. Moreover, the problem is not just a matter of the brand. Even within the same brand, the way in which users interact with different models may vary considerably. In the case of Nokia, for example, it is not the same to use a Nokia E61, an N95 or a 9500.
The design of the user interface is thus key to the success of a project, and unfortunately it is not possible to opt for a standard model for all handsets and all users. Success, then, depends in the first place on the performance of a target study of application users. The next step is to analyze handset market share in order to prioritize and focus work on establishing interaction patterns based on the terminals that are most popular with the target users in the project. Finally, an in-depth study must be carried out to determine the information architecture, the interaction model and, of course, the graphic design applied. In many cases, the conclusion is that the project must be undertaken in more than one way, which involves the creation of different clients for different handsets and users. The first decision, then, is whether to opt for a rich client (i.e. a high-performance, advanced-functionality, though not necessarily complex, application installed on the handset itself) or for a browser client (i.e. pages displayed in the handset’s browser). Each alternative has its own advantages and disadvantages, and the decision is far from trivial. In many cases, it may be necessary to opt for both and create different versions of the same product (normally with differing performance). At Kynetia we have a long track-record in the development of rich clients using the following technologies:
Kynetia users market standards for browser clients.
Server-side mobility
Kynetia Mobile Video Server's client
It may sound contradictory to talk of server-side mobility. However, there is no such thing as a good mobility client that is not supported by a good server. In reality, it might be thought this was possible, and indeed it is, but only where the applications are autonomous, like single-player games, for example, where the user competes against the telephone but not other networked users. As soon as the application requires connectivity, it becomes necessary for a server to support client needs. Our extensive track-record in the field of major corporate architectures supports Kynetia’s highly competitive positioning in this area, since we are able to provide our clients with complete, end-to-end solutions from the user or client through intermediate layers to legacy systems. Some of the mobile server platforms created by Kynetia are discussed below:
ConclusionAt Kynetia we have a long track-record of mobile projects in the financial, remote healthcare and telecommunications sectors. The know-how gained in mission-critical financial and remote healthcare projects (given the stakes involved) and in scalability for mass-market projects in the telecommunications sector is an unquestionable source of value for our clients. |