Our Products

Why don't you support my OS?

by Marc

With so many great mobile operating systems out there, we often get asked “Why don’t you support my OS?” Like my previous post about upgrades, I hope this one will help shed some light on the challenges of supporting an operating system!

We get requests for Mac, Blackberry, Symbian, and Linux versions of our software every day. These are all great operating systems and they have a lot to offer. In fact we’d love to offer our products on all of these OS’s. Unfortunately, there are some big challenges!

New Development Environment That’s a fancy way of saying that we’d have to write the program from scratch! Each OS requires us to write programs with a different set of tools. What is more, for some OS’s you need to write different versions for each variant of the core OS. Our programmers can certainly pull this off, but it means a major investment in time and resources.

New Devices As soon as we venture into a new OS we have to outfit ourselves with the devices to test on AND for our support staff. Emulators (programs that will fake the OS on your Windows PC so you can run software) exist but unfortunately these are not 100% reliable. To release software that really works well you have to test on a real device.

More Upgrades Writing updates and upgrades requires more and more time with each OS you add. So when we add a new feature to one device, we have to add it to the other devices, and on each device the feature has to be added in a different way since each device has a different development environment. Suddenly, the time between upgrades gets even longer!

Lots More Software Testing We test like crazy here. We admit, we don’t catch every single bug, but we like to think we do a great job of testing. For instance, with every major release we individually check every field on every card type in eWallet to verify that it accepts and retains data. We do this on every major device and OS variation of every OS we support. For instance, on Pocket PC we need to check: 2003 low res devices (portrait mode), 2003 low res devices (landscape mode), 2003 high res devices (portrait mode), 2003 high res devices (landscape mode), 5.0 high res portrait, 5.0 high res landscape, 5.0 square screen. This is just a tiny example but I think it shows the complexity of fully testing a piece of software.

Expanded Support Our support staff has to be up to date on every device we support. They need to know how they work, how the software works on them, and which device runs which OS.

Expanded Sales All of our resellers need to get the additional versions, marketing materials have to get prepared, and more.

I haven’t hit every issue here but I’m willing to bet you get the idea at this point.

Boo hoo! It’s hard. So what? Good question, and this brings us to the main issue. We can support other operating systems and devices. We’ve got some very talented people here and we could definitely pull it off.

The problem is that we, like almost every other company around, have limited resources (people, time, money). Supporting an additional OS means time that we can’t spend working on the OS’s we already support. It means time away from new software projects. It means thinning our focus.

So in the meantime, we will continue focusing on creating the very best products we can for Windows, Windows Mobile, and Palm OS. We may still offer support for other OS’s in the future, but for now we want to stay focused so that we can offer excellent products that meet our own high standards.

Share this article:


Upgrades anyone?

by Marc

There was a great discussion over at Pocket PC Thoughts about upgrades. Upgrades are something we spend a lot of time thinking about, and since this blog is a place where we can let you see behind the curtain, I’ll share some of our upgrade thoughts with you.

There are a few basic reasons we’ll do an upgrade. They are:

  • To support a new OS or an OS change.
  • To add a new feature that we think will really help our customers.
  • To fix a bug.

Furthermore, we also like to combine as many of these things into a single release as we can. The end result is that we just don’t release upgrades all that often. Sure we have bugs, but not many thanks to an excellent QA (quality assurance aka software testing) department. As for OS changes we stay pretty up to date on these and typically the change only affects a specific group so not everyone needs the update.

And as for features, we are really leery of ‘feature bloat.’ You know the kind of thing I’m talking about. Where suddenly your favorite word processor lets you play MP3s. So when we add or change something, we do it because we think it will absolutely improve the overall product, not just ramp up the feature list.

The problem we have is that there appears to be a growing perception in the market that a failure to offer regular ‘updates’ (regular meaning every 1-2 months) suggests that the company has abandoned the product. My personal theory on this is that the culture of ‘ready or not it’s out the door’ and ’the customer is our beta team’ software release schedules has led consumers to think that software is supposed to have tons of upgrades, patches, and updates.

We also don’t like having to upgrade the software we are using if we don’t have to. That is, the software other people make that we use. You never know how an upgrade will change your favorite program. Will it alter all your data file formats forcing you to stick with the new version? Will it drastically change or eliminate some favorite feature? Will a shiny new interface mean learning the program all over again? And if the program is working fine why do I need to spend my time downloading and reinstalling the new version of the software? What has the upgrade really done for me?

Not to mention the email issue. If we don’t inform people about upgrades, even ones that won’t significantly change their experience with the product, people get upset. When we do tell people about upgrades, we get lots of “Remove me!!” emails back from folks who see the upgrade notification as spam.

The long and short of it is this. Ilium Software is here to stay. There is no end to our software development days anywhere in the foreseeable future. We’ve got a product line that we’re really proud of and that we are constantly developing and improving. When we release a product, we do so with confidence that the customer can use it without trouble and that it won’t take 3 or 4 patches to get it working properly. And we aren’t going to ask our customers to upgrade until we’ve got a product that really offers them something great that makes it worth the upgrade effort.

Although we hope to speed up our release somewhat, we plan to keep doing what we’ve done so well for the past 9 years…providing our customers with the best software they can buy, right out the door, with the features they need and stability they can count on.

Share this article:


UMPC Beta Test About To Begin

by Marc

UMPCWe’re getting ready to release a new program for the UMPC and we’re looking for a few good beta testers! If you’re interested in giving it a shot, please email us as soon as possible. Due to a tight deadline it’s going to be a short beta so we’d like to get people started as soon as possible!

Just email us at beta@iliumsoft.com with your name, the model of UMPC you are using, and any other info you think would convince us that you’d make a good beta tester! Slots are limited so please let us know as soon as possible! Thank you!

And special thanks to James Kendrick over at jkOnTheRun for posting the announcement on his site as well!

Share this article:


Form & Function: A Developer's Perspective

by Marc

How important is appearance? Is it a vital part of any application design? Or just a nice thing to add if you have time for it?

There have been a couple of great posts about this subject today. One of them is at Just Another Mobile Monday and another at Treonauts. Both of these address the subject from the point of view of a user. I thought I’d take a second to discuss it from the developer end.

Creating a great looking app is actually something every developer (well, every developer I know anyhow) wants to do. Actually doing that, though, is something else altogether. There are plenty of roadblocks to making this happen.

Resources This is an obvious one and it affects a lot of small software houses. Designing a really good looking interface takes time and money. If you don’t have the skill in-house, you need to out source and that requires a serious investment. …

Screen Real Estate This is something both of the articles I mentioned talked about. Mobile software needs to take full advantage of the limited screen space mobile devices offer. The challenge here is that a good looking interface takes up space. While it can make the use of space more effective in some cases, more often it uses up screen space that cannot then be used to display data/content/etc..

Making it Work Pretty is one thing. Pretty and functional is another. It is a serious challenge to come up with an interface that not only looks good, but also does its job! (Anyone remember the old IBM commercial where the guys were showing off the animated flaming logo on the website but the site couldn’t handle customer orders?)

“Microsoft Says…” Or “Palm says…” or “HP says…” There have been many times when we’ve wanted to do something a certain way, but in order to achieve that all important approval from the powers above us we had to do it in what we thought was a less effective way. (Ever wonder why so many Windows Mobile apps don’t have an Exit/Quit function?)

Planning for the Future And last of all, when you put a beautiful interface like that onto a product, you’ve just set in virtual-stone how that product will work. Need to add a button for a new feature? Time to redesign the entire interface! Discover that the field isn’t big enough? Gotta order a whole new skin!

OK, so it’s hard to do and there is lots standing in the way. You probably get that by now. The question of course is how much should developers care?

In my opinion, a lot. A plain text data feed has its place but for those programs we use while we’re on the move, over and over throughout the course of our day, it has to be a product that treats us like human beings….not data processors.

For Ilium Software, this is something we are always looking at and as we move toward the future, it’s something that is becoming increasingly important in the evolving mobile software marketplace. It costs money. It costs time. But hopefully in the long run it will pay off.

Share this article:


You got "Getting Things Done" in my ListPro!

by Kevin

Ten points to whoever recognizes the advertising throwback in the title. “Getting Things Done” is a methodology developed by one David Allen to help create a ’trusted system’ for tracking what you need to.. get done.

GTD focuses on helping you dump your brain into this trusted system, so you don’t leave obligations looming in the black uncertainty raincloud over your head. If you don’t have time to read his book, you can probably get a good sense of how the core of GTD works by looking at this flowchart [PDF file, 30KB].

GTD is pretty popular with geeks, probably because it takes quite a bit of fiddling to get it done (geeks love to fiddle with things, in my experience), and because it’s a “Life Hack”, a way of optimizing your life to make things work better.

GTD is also something that is basically a bunch of lists. We make a product called ListPro that is very good at making bunches of lists. So inevitably, the two will collide. For the collision, keep reading after the cut thingy below.

Disclaimer: I am not the master of GTD. I am still ’trying it out’, so to speak, figuring out what the best way to implement it is. That’s one of the downsides of GTD - there’s no 100% right answer for how to make it work. The important parts of GTD are:

  • Making a trusted system, that you can rely on 100% without thinking
  • Making a trusted system, that you can rely on 100% without thinking (is there an echo?)

If you can’t rely on your GTD system, then you’re no better off than before you tried implementing it. This is one on of the downsides of a lot of organization tips and tricks - you have to do it, and you have to stick to it. One way to help you stay stuck is to find a system that’s comfortable for you. I’m still looking - so far, I’ve tried LifeBalance, the eerily-similar MyLife Organized, our very own ListPro, and am about to tack a program called Ultra Recall. If you want a good smattering of GTD aids in one spot, check out this blog post on 52Reviews.com .

Disclaimer 2: I don’t think I’m going to use ListPro for GTD. This doesn’t mean you should stop reading. If you like ListPro, and want to do GTD, give it a shot. You can certainly do it, and it may work perfect for you. I just feel like I need to say this so I’m not purely saying ListPro is the best thing since sliced bread. It’s like how I drive a Toyota - I don’t hate other car companies, I’m just familiar with them and found my car to suit my needs. ListPro works great for testing checklists, daily process lists, call logging, my groceries… just not my GTD.

Anyway, enough yap. I present to you the ListPro GTD template. [Warning: 122KB .CLF download, requires ListPro!]

Just download that file, stick it wherever you want, and peruse it. You’ll find helpful hints written by me.

Is this the only way to use ListPro for GTD? Probably not. Is it the best GTD implementation there is? Probably not. Is there a best GTD implementation? For you, yes. For everyone, no.

So go get some things done. [Kevin now checks off the ‘push publish button in Wordpress’ Next Action…]

Here are some tips:

  • On a Pocket PC, to sync your GTD list, make sure you have Files turned on in your ActiveSync settings, then just drop the GTD template into your Pocket PC’s synchronized My Documents folder.
  • On a Palm, you’ll want to open your regular ListPro list file on your desktop and go to Tools -> Import Lists…, then point to the GTD file.
  • Get familiar with the shortcuts for copy and paste (Ctrl-C or Ctrl-X if you want to cut, Ctrl-V for paste), since you can’t drag items between lists.
  • If you want to change your columns, you may need to re-build the entire template. This just is a limitation to how ListPro works - each List has its own format, and you may not be able to copy items between lists of different formats.
  • If you really want to stick with ListPro for GTD, make a shortcut for your actual GTD file and place it in your Start Menu’s Startup folder. This will launch the file whenever you boot up or log into Windows. Then, right-click on the shortcut and pick Properties, and assign a keyboard shortcut. Whenever you want to add something to your list, just press that shortcut and ListPro will open right up - it should open up to displaying your Inbox, but it may change to whatever list you had been working in last.

If you make modifications to the template or have any feedback, feel free to either send a message to Ilium Software or leave a comment below! I’ll be glad to post different templates or update it based on user requests.

If you have any problems getting this to work in your ListPro, or have any other problems with our software, just contact Ilium Software directly and someone will help you. I’d like to put my email here, but I haven’t figured out how to effectively spam-proof it in Wordpress yet.

Share this article:


NewsBreak and ListPro Get More Action

by Ellen

A great review of NewsBreak by Todd Ogasawara showed up on Microsoft’s website. Thanks very much, Todd, for cheering up a day that really needed it (though the weather’s beautiful) (though not as beautiful as it no doubt is in Hawaii).

ListPro got a bunch of sales from being featured on Bits du Jour, and one very nice comment about how well it runs on Kubuntu under wine. I’m fuzzy about what that is, but am very happy it works!

Share this article: