JAMM Interviews Chris McKay of Lakeridge Software


Chris McKay of Lakeridge Software

And the JAMM Developer Interview series rolls on…

We recently had the opportunity to sit down with Chris McKay of Lakeridge Software.  Chris, the author of the classic task managing, UI skinning WisBar Advance and the customizable Today alternative WisBar Advance Default (interestingly, WAD was the first handheld program Doug ever bought!), has agreed to answer several questions for you.  Please check out the interview below, as Chris shares how he became involved in developing for Windows Mobile, how WisBar Advance was born and his thoughts on mobile computing.

As you start with the interview, please note that the questions in bold are presented by JAMM, while Chris’ responses are indented.

Hi Chris!  Thanks for agreeing to this interview.  Can you tell the readers at JAMM a little bit about the history of Lakeridge Software, and the mobile solutions it offers?

I started Lakeridge Software in October of 2004.  The original product I developed was WisBar Advance version 2.  The very first WisBar program was originally developed by a Japanese developer.  When he got sick, he gave out the source code to a few individuals.  One of those was Marc Pelmar.  Shortly after that, I started helping Marc develop WisBar.  But, it became obvious that many of the users wanted to take it a different direction.  So, I got permission to create WisBar Advance version 1 and I went out on my own.  After about a year, I completely rewrote the program as its current state wasn’t allowing me to develop it in the direction that I wanted.  Because I couldn’t afford to pay my bills, hosting fees, etc. I decided to start charging for it.  About a year later, I created WisBar Advance Desktop as I wanted a more powerful Today screen.

How did you get into mobile developing?

How I got into mobile developing is a little bit of a longer story.  When I was in the fifth grade my friends and I taught ourselves how to program computers.  Mostly this was done by reading magazines and looking at the source code for various programs on Apple ][e’s and TI-99/4A’s.  Over time, I learned how to program in C/C++, as well as Java, Pascal, Delphi, HTML, PHP and Visual Basic.

During high school, I learned how to write programs for my TI and HP48g calculators.  My friends and I would share a few games that we had written with each other.

When I was 21, I got a job with Franklin Covey in their technical support department.  Part of my responsibilities was to support Palm Pilots.  I learned to like having a PDA around, but I never actually started writing software for them.  However, about three months before I left the company, we got our first Windows CE 2.11 devices.  I quickly got more interested in them because they had the Windows interface on a handheld form factor.  So, I started learning how to write software for Windows (I had been a DOS programmer up to that point).

I didn’t actually start fully writing software for the PocketPC devices until PocketPC 2000 came out.  I had quit Franklin Covey, so I didn’t have access to a device anymore (other than my Handspring Visor).  But, my new boss gave me an iPaq 3600.  I quickly started writing software, but I didn’t distribute anything.  It was then that I met Marc Pelmar online and was able to examine the source code for the original WisBar program.  After that, I kind of went crazy programming for these things.

What makes your programs, Wisbar Advance and Wisbar Advance Desktop, unique?

That’s an interesting question.  I guess part of what makes them unique is that I wanted to make my device as customizable as possible.  I’m one of those people who likes to change the appearance of my computers and handhelds so that they fit me, rather than the other way around (this probably explains why I used to use LiteStep and am a big Linux user).  I liked the idea of the original WisBar, but I wanted it to be more powerful.  So, I learned how to hook into the OS and make it do what I wanted it to do.WisBar Advance Desktop is unique because it gives full power to the end user to customize the Today screen in any way they want.  While other products were good (and there still are many today), they don’t give me the flexibility I wanted.  So, I wrote it up in such a way that the only limit to the program was your imagination.  While that doesn’t exactly make it very user-friendly for everyone, there are many who think the same way I do.  So, this program is really for them as well.

Since you are specialized in the Windows Mobile arena right now, are you considering supporting any other platforms in the future?

Yes, I am.  I am actually currently writing a program that for Windows Mobile 5 and 6, Windows Phone 7, Android, iPhone and even the desktop.  I’m also considering writing for WebOS.  Because the nature of the mobile space can change from moment to moment, I want to be flexible enough to give the users what they want.

Can you tell our readers anything about upcoming projects you are working on?

Currently, I am running a public beta for WisBar Advance v4.  Also, I am putting the finishing touches up on WisBar Advance Desktop v2.6.  Unfortunately, due to the fact that writing custom shells seems to be nearing an end, these will probably be the last versions I write for Windows Mobile.  However, I do plan on supporting them indefinitely.

I’m also currently writing a new program that will run on the major OSes (WM5 and 6, Android and iPhone).  It’s not going to be a shell, though.  That’s all I’m going to say about that right now :) .

With all of the interesting twists in the mobile operating system arena, what predictions do you have regarding the future of mobile computing?

I honestly think it’s going to become much more popular.  Even though I don’t always see eye to eye with Microsoft, I believe that they truly got the idea that computing was a personal thing.  The concept of the smartphone is the embodiment of this.  There was a time where I did everything on my PDA (with the exception of writing software on them).  Though the current generation of smartphones has kind of lost that ability in some ways, I believe that one day they will be the primary computing device for everyone, with the laptop and desktop used as secondary devices.

Is there anything else that you would like readers to know about Lakeridge Software, your software or yourself?

I guess I’d just like them to know that I believe that their devices should be tailored to them, not the other way around.  I hope my software has helped make their experiences better and more enjoyable.  I’d also like to thank them for all of the support they have given to me throughout the years.

We really hope that you enjoyed our interview with Chris as much as we enjoyed the opportunity.  We really appreciate Chris’ time.  If you have any questions for him, please leave them in the comments section below and we’ll be sure that he has the chance to read them!

Be Sociable, Share!

Related posts:

  1. JAMM Interviews Chris McKay of Lakeridge Software – Coming Soon
  2. Lakeridge Software – WisBar Adavance 3 On Sale Now!
  3. Lakeridge Software Getting Into Android Development
  4. JAMM Interviews SPB Software
  5. Lakeridge Squashes Bugs, Optimize WisBar Advance 2.


2 Comments

You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.


breley
Mar 15, 2010

Interesting interview. So that’s what Chris looks like without his shades. ;-) I’ve been using Wisbar Advance and Wisbar Desktop for a few years now. They really improved the the usability of my Axim X51v and now reside on my HTC X7501. I’ve most partial to Juni’s skins for the apps as well.

Trackbacks

JAMM Interviews Chris McKay of Lakeridge Software | ClintonFitch.com | Reviews of Everything Mobile!

[...] In the interview Chris discusses happenings that are going on at Lakeridge from a development perspective and Chris provides his view of the mobile space as a whole.  All-in-all, well worth the read and a visit over to JAMM. [...]

Leave a Reply

You must be logged in to post a comment.