It’s already in there! If you’re editing a card in eWallet on the Blackberry, press the menu button (Blackberry button; I guess the dots look like a blackberry’s fruity juice-filled… segments?) and pick “Password Generator”.

You can also “Paste New Password” which uses the current settings in the password generator to generate and paste in a password without sending you to the PassBuilder options.

With the new Iphone version I still think that Ilium e-wallet is the best product in its class. I am looking forward to the introduction of the OS-X version and I agree that they should insure they have a properly working version before issue. I do hope that that they are able to do so sooner than later. I have a dozen computer eager for the new product.

I DID provide ETAs, but put caveats around them – we’ve been delayed many times, but have finally released the product. At least I kept thiem posted and gave them some reasons for the delays.

If people reacted like some people Kevin mentions, then no matter what you do; you lose. People like me and the majority of your customers would read AND TAKE IN delays, issues, reasons etc.

I say b0ll0x (sorry) to the people who react they way Kevin describes – but you should worry about the reasonable people..

Warmest Regards
Henry

I use a program called Bibble to ‘develop’ RAW images from my digital camera. It’s an affordable program that offers me most of what I want to do to an image, while adding some neat extras. However, I’m a Mac user, and their current version 4 for Mac is… quirky. And when I mean quirky, I mean it’s full of bugs. It almost has enough bugs to make it not worth using, but the benefits tend to outweigh my annoyance so I keep using it and haven’t bothered switching to something else like Aperture, Lightroom, LightZone, etc. Switching means a learning curve and more money spent, and for a hobbyist like me, I haven’t tipped over the edge yet.

Bibble is working on version 5, which is a very significant upgrade. Unfortunately, they couldn’t meet their projected release date. On their support forums, there was a big outcry over this. There are a lot of reasons why the development took longer than they thought (for example, they do their own RAW processing instead of relying on Apple’s built-in OS support for it), but basically they tried to get it out by the end of 2008 and just couldn’t do it.

Some vocal users on their forums offered up severe tongue-lashings and “I’m going to get something else! Hmmph!” comments. There were a lot of threats of abandonment and, “you guys are full of it, you are morons and stupid and I can’t believe you would ever take money for software you develop!” I’m serious. You wouldn’t talk to your mother the way some people talked to the developers.

Because they couldn’t release the finished version when they wanted, and because community members begged and threatened, Bibble released a ‘preview’ version with reduced functionality. I eagerly downloaded it, because I want to try a version that was built from the ground up to work properly on OS X.

Unfortunately, ‘preview’ is exactly that. It supports RAW formats from a couple camera manufacturers (like Canon and Nikon), but not my Pentax DSLR. As a result, the preview program is absolutely useless to me. I was disappointed for about five minutes, and then went back to using the old version and waiting.

Could Bibble have really squeezed out the version 5 upgrade on time? Are they wrong for waiting until it works right before releasing it? I personally think, ‘No’.

This stuff isn’t easy. As an employee of a software company, I know that even though I’m not an actual developer. I’m giving Bibble a break partly because ‘I know how it is’.

Time Table for Mac eWallet: We originally tried to post an estimate for release. In addition, we did everything we could to make it clear that was the date we were shooting for and not a promise. The challenge is that people took that as a guarantee of release date. I feel like we’re stuck between a rock and a hard place. If we give an estimate, people take that as a promise and then hold it against us if we fail. That exactly what happened with Mac eWallet. If I don’t give a date, people are frustrated because they don’t know what is happening.

ListPro: The reason I’m being cagey about this is that we have decided to do something a bit more than a mere reader, but with over 100 list management apps in the AppStore, we simply can’t talk about the plans (as much a I want to.) Doing so would be to hand a competitor a spec they could use for their own products.

Apples2Oranges and Development Time: You can only put so many people on a project. At some point they just get in each other’s way. We have multiple developers and contractors as well. Having someone work on a different project does not directly take away from time we could spend on another project. I REALLY wish I could throw everyone we have at one thing to get it done, but it just isn’t possible. So, we continue to produce other smaller short-term projects with the other folks. (Including a number of Windows Mobile projects underway.)

Hope this helps!

PS: I’m in jury duty all week but when I get back I’ll try to do an entire post about these issues.

In the meantime, however, you have released a new product (Apples2Oranges). Could some of that time have gone toward creating ListPro? Given the fact that it has been over 6 months since you started working on the product, I would hope we would get an update on the status of ListPro soon. Marc—you are correct, I have loved the product on my PC and WindowsPC. That is why I keep pestering you for an update of the software.

The eWallet for Mac is different, you don’t need to submit that to Apple before release. We won’t hold you to any dates (we all know about last minute glitches). Please just give us some infomration, thoughts, any kind of dialogue in regards to these products.

Thanks.

However, the lack of any real news is discouraging. I do understand the philosophy behind the curtains, but I do not agree with it. I personally think it does a greater disservice to customers – both existing and potential – to not know what is going on and when they can expect updates to their applications – that is one of the primary factors I now use when considering software purchases. It’s not enough (to me) to know that it is happening – I feel like I deserve to know something since I am a valid, current and paying customer that is supporting your company.

All that being said, I will likely remain a loyal customer as I really enjoy Ilium’s products and the value and feature sets they provide, but it doesn’t mean I’m a necessarily happy customer at this point, and that’s the beginning of a bad trend.

So Ilium, I personally feel that you need to re-think this overall strategy – it serves no one and the lack of overall information to the customer-base is so very frustrating. It just doesn’t feel like a good customer/vendor relationship this way, and in fact, I feel a bit strung along and that doesn’t make me feel good about my future purchases.

Please take this as constructive criticism – it’s not intended any other way.

Thanks.