The solution presented in the previous examples is just a draft of functionality that could be delivered in a real system. Below we list some of the enhancements that should be made to turn the sample application into a comprehensive mobile banking solution.

Some of these can be achieved within the Lemonade framework, others require changes to the framework itself. If you are interested in using Lemonade, take a look at our services.

Lemonade neatly integrates with an excellent solution called J2ME Polish which, among other things, can be used to create branded GUI - see more. It is possible to replace the standard MIDlet classes delivered with Lemonade with a custom, branded implementation.

It is also possible to extend the MIDlet with classes that handle sound playback - for example to use sound notifications.

Users of MIDP2 phones could benefit from better security during transfers.

In addition to a secure HTTPS connection, the transaction could be secured using Blue SMS messages. Not just the connection would be encrypted and secured, but the bank could also verify that the application is running from the client's mobile phone by sending a confirmation message to the client's phone number. A sample scenario:

• user launches "moBank" application, enters "moAccount" and starts a transfer - an Internet connection via secure HTTPS protocol is established,
• the server responds with a "Please wait..." message and sends a Blue SMS message to the registered user's phone number,
• the mobile phone receives the Blue SMS automatically passing it to the "moBank" application - this closes the "Please wait..." message and connects to the server to send the secret operation id received in the Blue SMS.

Some banks already do this for browser based online transfers, but the client has to tediously retype a long sequence of numbers from the mobile phone into a web browser window. With Blue SMS messages the confirmation SMS messages do not clutter the phone's inbox and the user is freed from retyping secret numbers.

The current version of Lemonade only handles Blue SMS messages up to 140 bytes long.

It would be possible to send and receive messages of an arbitrary length, split into a number of SMS messages that would be merged by the MIDlet. This would make it possible to send complete services through Blue SMS messages, thus freeing the user from the need to start a GPRS connection to update the application. For example, the moAccount service is ca. 1.5kB (including the installer) - this adds up to about 10 SMS messages.

Clients of moBank could update their application during a visit to the bank through a Bluetooth connection.

It would be enough to extend the user application to include a Bluetooth update service and to install Bluetooth infrastructure in bank offices. A good Bluetooth hardware solution is delivered by BLIP Systems.