I just found out about this amazing new product called MojoPac that lets you shrink your personal computer so it fits in your pocket! If this sounds like a line from a really bad infomercial, trust me, it’s not; and if it doesn’t sound entirely believable, well, it is. Okay, MojoPac won’t literally shrink your computer, but it does let you install any of your programs, files, and personal settings on devices like iPods or USB drives, so you can access them safely from anywhere. Now, to switch back to infomercial mode: But wait, there’s more!
If you have eWallet on your Windows PC, you can install it on your MojoPac device and carry it with you, along with any of your other personal Windows PC programs and settings you want to add to MojoPac. When you combine the already strong security of eWallet with the safety of a MojoPac PC, you never have to worry that your personal information can be seen by anyone but you. When you disconnect your MojoPac device from another computer, all your data stays with you. You can look at your eWallet files just as if you were on your home computer, and it all stays safely on MojoPac.
Visit the MojoPac website to learn more about how MojoPac works, and what devices you can carry it on - including iPods, USB flash drives, and even some cell phone models.
You can also check out our Windows PC eWallet information to find out more about the program, and how it works alone or with MojoPac to protect your information and make it easy for you to access when you need it.
Every once and a while, Ilium Software tech support gets a heads-up about an interesting and unexpected use of one of our products. We aren’t the only ones; Patrick at MicroISV on a Shoestring had the same experience and his story prompted me to think.
Sometimes the use case isn’t much of a stretch; ListPro is a program to make lists, so it’s hard to find a use for ListPro that isn’t obvious by definition. Prayer lists, scavenger hunts, web bookmarks, flight checklists… they’re all still just lists. NewsBreak is the same way; RSS and ATOM are usually used for simple ’newspaper headlines’, but all sorts of information such as your NetFlix queue, Gmail account, eBay search results and weather reports are available via RSS. These uses are just part of what NewsBreak is designed to do.
eWallet, on the other hand, is really designed to be a program to hold your sensitive personal information like passwords, credit card numbers, bank account numbers, frequent flier mile cards. That’s it; you put personal information in, eWallet encrypts it under one password. That doesn’t stop people from coming up with their own uses.
Just yesterday, we had a user mention that she used eWallet to keep track of things she wanted to buy on the web. She would create cards with the backgrounds set to a picture of a particular item, with the weblink to the item and a description in the notes. That way, she could see at a glance exactly what something was, instead of having to go visit the website to figure out why it was in the list.
This is not something eWallet was intended to do, but it works and made the user happy. The ‘pictures of stuff to buy’ list works because eWallet supports both card background graphics and Picture Cards (useful for pictures of your dog / cat / gerbil with fruitless dreams of freedom / kid / favorite flower pot / car / boat / that really big fish you caught that was thiiiiiiiis big, really! / etc.) You know, stuff you would keep in a real wallet.
It also brings up the great can-of-worms question, “Should we pursue this with eWallet?” I definitely don’t have the answer. Questions like these are great, because they open up all those weird little opportunities you - the developer, or tester, or anyone else in software development - wouldn’t necessarily think of on your own.
A big challenge developers face are requirements given to them by OEMs (the people that make your hardware) and demands from folks like Microsoft and Palmsource. There are times when these requirements conflict with what we want to do or with what customers tell us they are looking for. Microsoft just put up a great blog post about one of these requirements (the missing Exit feature in Windows Mobile discussed at the Windows Mobile Blog).
Having read that, I figured I would share a developer perspective on this often frustrating topic…
So the easy answer is to just ignore the requirements. I mean, we’re doing this for the customer after all so why would we include some annoying feature just because we’re told to? Isn’t it customer purchases that keep us in business?
Wellll, sort of.
The problem is that in order to get those sales, there are a lot things that have to happen in the background. A big one, is getting that vital stamp of approval from Microsoft, Verizon, or whoever is sending down the requirements, and you only get that stamp if you do what they want.
So why does this matter? Glad you asked!
There are a bunch of reason but here are a few from the top of the list:
Certain online stores require application approval to get listed. No stamp of approval and you don’t get listed, or if you do, you get the second balcony seat with an obstructed view.
If you want a lucrative ‘in ROM’ deal (that is, the application comes installed on every device the OEM makes) you have to follow their rules. The OEMs only play with folks who are on “their team.”
Large volume purchasers may avoid ’non-approved’ applications because if the application couldn’t get approval, they don’t feel that they can trust it.
There are plenty of other examples but you probably get the idea.
The Biggest Reason There is, however, a bigger reason.
We need the Big Guys to like us.
OK, maybe I’m sounding a bit like the high school outcast longing for the approval of the in-crowd, but the fact of the matter is that we gain access to a LOT of support by going along with the Big Guys’ game.
Here are some examples. Let’s say an OEM is about to make a major change to their hardware. Do you think they tell everybody in advance? Or just their “friends”. If that happens and we don’t know, our competitor now has a working version (because they played by the rules) and we don’t, leaving us in the dust.
Or perhaps an OS developer has decided to chop out some bit of code our applications depend on. If we haven’t played by their rules, they have no reason to let us in on this. When the OS update comes out our product suddenly crashes on every updated device.
Or maybe it’s just as simple as an oddity in the OS that we can’t figure out how to work around. By staying on the side of the Big Guys we have the opportunity to contact them and say “Hey…how do we make this work?” You only get those opportunities if you’ve been going along with their game.
In each of these cases we take a blow to sales if we lose the Big Guys’ support, and if there are too many of these blows we end up being one more memory in the sea of dead Mobile Software developers.
And this matters to our customers because if we’re out of business that means no more upgrades, no more support, and no more new software from a company many people have come to depend on.
So that’s why our Pocket PC applications don’t include an Exit option, our WM 5.0 applications now use the two menu system without toolbar icons, and our Palm applications have Unfiled categories. Maybe it isn’t the way we would have done things, but what it does is allow us to continue making enough money to stay in the software business. It’s part of the reason that over 9 years after we opened our doors, we’re still coming out with updates, offering top quality support to our customers, and producing great new applications for mobile devices.
PS: And don’t tell Microsoft, but clicking CTRL+Q on your Pocket PCs onscreen keyboard or tapping 7 in the About screen of our software on a Smartphone, will “truly” Exit most of our products! :)
I had to share something that came up in a support call yesterday. It’s either really horrible or incredibly funny depending on your point of view.
We received a panicked call from someone trying desperately to access an eWallet file that they didn’t know the password for. This isn’t all that unusual. We all know that it’s easy to forget the “really good” password you came up with (one of the things that makes eWallet so handy!) The problem of course is that eWallet, being a secure information manager, really IS secure. If you forget your password there is NO backdoor, NO way to reset the password, and NO reasonable way to hack the wallet*.
In this case though, the problem was that Company A bought out Company B and laid off all the IT staff from Company B. Unfortunately for “A”, the IT staff at “B” stored all the vital IT info in eWallet and no one bothered to ask them for the password when they laid everybody off.
Needless to say, panic ensued. As a person who knows how bad it would be if we lost access to all our passwords, I can feel their pain…but on the other hand, as a guy who has seen his friends dumped out on the street during a merger, I can’t help but snicker.
\* There are numerous articles about hacking 256-bit encryption. Estimates to do so typically involve a few hundred thousand computers linked together and working continuously for tens of thousands of years. Yeah…pick a good password and you’re all set.
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.
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.