My Photo

About Me

  • Hello you. I'm a 38-year old MSc student, studying Advanced Computer Science at Sussex University. I'm especially interested in Internet and mobile software, sensors and pervasive computing, user interfaces, and the process of developing great software.

    Before that I spent 11 years running Future Platforms, a software company I co-founded which makes lovely things for mobile phones, and which I sold in 2011.

    I read a lot, write here, and practice Aikido and airsoft. I live in Brighton, a seaside town on the south coast of the UK, with two cats and a clown.

AdSense

Stalk Me

  • Email me:
    twhume at gmail dot com
Blog powered by Typepad

« Work work work | Main | Flash Lite 2.0 »

October 24, 2005

Comments

Simon Cavill

Interesting - We run mobile payment services for mobile operators and other content owners and utilise a Java MiDP 1.0/2.0 applet as one channel. The app is very simple in look and feel and uses 3DES encryption. The real issue for us is that if you do go for a vanilla app to cover a wide range of devices, it looks sooo ugly in both look and feel due to the limitations of the early (read widespread) devices... The only alternative is to do as you have and create multiple versions for families of devices - Its horrible which ever way you look at it - No wonder most of our clients default to SMS....

We are now working with games companies etc putting our payment kernel inside their apps, so they take on the pain of phone compatibility!!!

Great Blog,

Simon

Tom Hume

Simon - another alternative is to create your own app platform, built on top of MIDP. This is what we ended up doing (see http://www.futureplatforms.com/fp/cactus.jsp) and along with a well-tested methodology for managing ports, lets us do tightly defined custom UIs across many devices.

Interestingly, we've just gone through a process of looking at outsourcing porting. Thus far it looks like the cost savings of using offshore labour are mitigated by the need to support, document and manage the porting process; and if it's been built sensibly with portability in mind then the original development team are better positioned to handle ports and can do them *way* quicker.

But it's early days and I suspect this may change over time.

The comments to this entry are closed.