Zaxis Technologies

Zaxis® is the worldwide leader in mobile application deployment technologies that enable efficient development and delivery of high quality user experiences across global wireless networks and devices.

Monday, October 03, 2005

Post CTIA thoughts

First of all, thanks to all the Disney people for putting on a great party, and inviting me!!! I met some very interesting new people, and reconnected with various others.

There were current customers, potential new customers, VC's (always important), carrier people, and handset people!

Although I was at Moscone for only a day, I did get a chance to speak with a bunch of people and check out the exhibits. Motricity had a booth, but I didn't get a chance to talk to them. I am still curious what role they are going to play in the overall "food-chain".

Kyocera Wireless had a cool booth and a cool new slider phone!

What was the greatest news in my opinion? In-fusio getting Halo, by far! Outstanding!

Saturday, October 01, 2005

To BREW or not to BREW

So what is up with BREW? From what I hear from the trenches, and being in our position, we hear lots, it’s become more difficult to get BREW apps, mostly games, accepted into Verizon. Apparently there are all sorts of bottlenecks being created and publishers can’t give us good predictions as to what and when they think might finally be accepted. I hope this is worked out soon so that we can get back to providing more BREW ports.

Lately at Qualcomm, there are more and more problems getting working BREW handsets at the BREW labs, and the ones for non-US carriers are totally not available. So, is Qualcomm no longer supporting those markets? What’s up? I know some of this is caused by the 911 regulations, but I would think that Qualcomm could get some of the other network bay stations in order to support the BREW labs.

We are now forced to port to J2ME phones, we are actually doing about 50% BREW and 50% Java – that’s a change from about 90% BREW and 10% Java. The publishers seem to be able to get their applications into t-Mobile, Cingular and Sprint more easily, and so they are choosing that route over BREW.

The good news is that the handset guys are supporting BREW, with Nokia even getting more CDMA/BREW phones out. But on the other hand Kyocera is releasing the KX 5 on Virgin? Good for them, but...

Ok, one more with a pic from CTIA 2005

I took that when I was resting at the end of a crazy/busy day at the Moscone Center. I used my LGVX 8000 to take the picture.

Lots of people in suits this year. Is the industry getting serious? Hmm...

Just another week

I feel closer to getting it "all together" for some reason. In the last week, we made great progress in attracting a couple of local handste manufacturers with our ability to "profile" or "characterize" handsets (BREW enabled). This is going to be critical in going forward and getting the accurate handset data. Especially if we can discover and solve any of the device issues up front.

Greg is making quite a bit of progress in integrating the handset data into the overall environment to create a comprehensive 'priZm' solution that we can start licensing early next year. This is also critical.

All this made me feel very good about our direction and finally moving closer to our ultimate goal!

Saturday, September 24, 2005

The problem of porting and some ideas on how to help

The difficulty and expense of porting and the handset expertise required have become major barriers to porting and thus to the full distribution of many games and other data applications.

The fundamental problem lies in how the developers approach the development process and how well they adhere to good programming methods and code standards. Portable code is the key to fast and problem-free application turn-around

Some high level suggestions and things to keep in mind when developing for the mobile world:

  1. 75% of phones have 64K or less space for Java games
  2. Porting/testing can take up to 80% of total development time
  3. Remember - your code is not for your eyes only! Keep in mind that some other developer will need to understand it to port it
  4. Comment your code to make future porting easier
  5. Create common base code for all platforms - BREW and J2ME
  6. Create a good project directory structure - keep it clear and keep it extensible
  7. Write an application framework that is reusable, portable and extensible
  8. Develop a sophisticated configuration management process
  9. Isolate platform and device dependencies, even if it means some extra work
  10. Properly document the steps necessary to build the application - again, it may not be for your eyes only
  11. Structure your code in such a way that the porting developer touches as little of the source code as possible when doing ports. The less code is changed, the smaller the chance of introducing new bugs!

Wednesday, September 21, 2005

Just remembered this fun picture from this year's BREW conference - San Diego, Seaport Village, June 2005. This is me with a couple of "clowns" just as the festivities began.

Posted by Picasa

Monday, September 19, 2005

CTIA Sept 2005

I will be attending the upcoming CTIA in San Francisco on September 27th. I am looking forward to meeting with our key customers and perhaps other partners.

I am most excited about renewed interest by Verizon Wireless regarding placing Zaxis on their MAC program. This will be the greatest achievement for us this year, if I can help move it along.

Currently we're completing various projects and are visiting with our customers to prepare for the next year which should be even more busy than this year.

I am also curious about some new content aggrogators like Motricity and their role in this market starting next year and how this will affect publishing on major carriers and for BREW in particular.

Mobile Deployment Experts

Posted by Picasa