Probably everyone who reads this blog has already seen this elsewhere, but in case not:
Our good friend and fellow mobile developer, Alex Kac, has written an Open Letter to Warez Sites in his forum, and asked some other developers to help publicize it. Of course I agree with what he wrote (or most of it - maybe not the “have a great day” part), and while I’m not at all convinced that this will change anything (do people really go to warez sites without realizing they’re stealing the content?) I’m completely behind any efforts to do anything to stop software (or any intellectual property) piracy, and happy to do whatever I can to help publicize the problem.
I’ve written posts about naming products before and I gotta say, it’s a tough job. You search and search for just the right name, think you’ve found something really cool, and then…well then you usually realize it’s taken…so you search and search for ANOTHER name, think it’s really cool, go with it and find out later that it confuses the heck out of everyone!
A great example (and my current naming challenge) are our Professional Editions. Our Professional Editions are just a bundle that includes the product for a PDA AND Desktop for one price. Unfortunately people constantly get the impression that there is some sort of feature difference. Maybe the “Professional” version has more bells and whistles? Better encryption?
Unfortunately I can’t blame them. Often a “Professional” version of something IS a version with a number of different features not present in the “standard” edition. Well, it’s time to clear things up.
We’re getting ready to select a new name for our Professional editions bundles. So far we aren’t happy with the results. The biggest problem is the names just end up really long. Then it struck me…just ask the world! Someone is bound to have a great solution to this problem. So anyone have any ideas, insights, or comments?
One of the toughest things to do as a (relatively) small software developer is to get the word out about your product. We don’t have a multi-million dollar ad budget or a marketing department filled with people thinking up clever new ways to let people know how badly they need our software. At the same time we have some great products that people get really hooked on once they start using them.
Eric Sink, a person in our industry who I have a ton of respect for, wrote a blog post today about a near disaster with his laptop. It no longer recognized his fingerprint and he couldn’t remember the ultra secure password he’d selected for it! I read articles like this one quite often and all I can think is “We have the solution! Why doesn’t everyone know about it??”
The Solution for Eric So just how could we have helped Eric? First, I’m going to assume that Eric either a) has more than one computer at home, maybe a desktop PC somewhere or that b) he could GET to another computer if he needed to. That said, here we go:
1. Eric enters his top-secret laptop password into an eWallet card.
2. Although Eric still needs to remember his eWallet password, because he has all his important passwords in eWallet he only has to remember that one password. Now the odds of totally forgetting become very slim!
3. Eric could even choose a handy hint in eWallet to at least push him in the right direction if he does forget his eWallet password.
4. Using SyncPro in eWallet 5.0, Eric can synchronize the wallet on his laptop with the wallet on his desktop computer. Even if he gets locked out of the laptop as he did in the article, he can still get the password from eWallet on his desktop!
5. In a worse case scenario, maybe his desktop fries out or something, he could have backed up his wallet to a CD or used SyncPro to back it up to a USB drive or remote FTP site. If he does this, by installing eWallet on any computer, he can open the wallet file that he has backed up.
Throw in some other precautions, like making sure at least one other person (wife/best friend/etc.) knows the eWallet password as well and now he never has to worry about getting 100% locked out of anything! Laptops, websites, bank accounts, with eWallet he has them all at his fingertips (pun intended. :) )
The Solution for Ilium Software
This one is a little tougher. Just how does a company like Ilium Software get the word out? In this age of a million choices it seems all to easy to have your product slip off into the depths of the internet and get overlooked by customers you could really help! Apparently we’re doing something right because we’ve been around for 9 years, but we want to do even better to ensure that we’re around for at least 9 more!
So please post your two cents on this one! We’d love to hear your ideas. (And Eric, if you’re reading, drop me an email! I’d be happy to get you a free copy of eWallet!)
One of the top requests we get for NewsBreak is that we download and cache the web pages that the “Read More” links go to. The reason people want this is that many news feeds don’t provide the full story. They just give you a teaser. If you’re off line this means you can’t read the entire story without going back online. Annoying, I know, especially for those feeds that only give you like one line of the story.
So why don’t we do it? I’m glad you asked! Read on for the full story…
How a Newsfeed Works
Before I go into the details I’ll offer the world’s shortest lesson on RSS. No technical details here. Just the nuts and bolts of where the content of a news feed comes from. When you subscribe to a newsfeed you get a specific bunch of content. We, as the news reader, have no control over this content. The provider determines how much you get, whether images are included, etc..
So if the provider only wants you to read the first two lines, all we can provide you with are the first two lines. If the provider sends the entire article, we give you the entire article! Unfortunately, most providers only send one or two lines of a story and then include a link to the whole thing.
The Economics of Newsfeeds
Why do they do this? Another excellent question! The fact of the matter is that these sites typically make money when people actually visit them. Unique visits, click throughs, ad clicks, and other typical “web money makers” provide the source site with income. If they send you the entire story, you never visit the site, and they never make their money! For many sites the news feed isn’t so much a service as it is a teaser to get you to visit the actual site!
The Trouble with Caching: Part I This brings us to the problem. If we start going out to the links in a news feed and grab the entire page that it leads to, we’ve just killed the potential income that the source site hoped to make. When you read the article offline not only can this bypass their metrics (means of measuring hits) but it may even eliminate the ads completely. Needless to say the providers
really really really
don’t approve of this!
Technical Note: Yep…this is a simplification but the general point is valid. The sites want you to visit, not download their pages.The Trouble with Caching: Part II
Here is the really ugly one though. Copyright. If we go out, grab an entire web page and copy it to your device, we’ve just duplicated copyrighted content.
Is this legal?
Maybe it is but maybe it isn’t. To my knowledge this hasn’t been played out in court yet (not in the situation we are in anyhow.)
Do I want Ilium Software to be the company CNN, Disney, Time-Warner, or others send their lawyers after to resolve this issue?
Do I need to answer this one? :)
And this isn’t just a legal issue. We’re in the business of selling software. Copyright is a big deal to us. There is no way we are going to do anything that even comes close to violating the copyright of someone else. It goes against our core beliefs as individuals and as a company.
The Moral of the Story
For now, I don’t intend to put page caching on our list of new features for the next version of NewsBreak. Anything is possible of course and we never close the door completely on a good idea. At the same time, until we hear something that solidly invalidates the problems listed above, it just isn’t something we feel comfortable doing.
I recently installed IE7, and for a lot of reasons, didn’t like it much. I’ve never managed to get along well with Firefox, but after spending some time with Opera, found that it worked pretty well for me. There’s a lot it doesn’t do - I do keep IE7 and Firefox both available as well, but I decided to use Opera as my primary browser. Given that Opera imported my IE bookmarks and that I only ever let IE save the passwords I didn’t care much about (things that I don’t really consider very secret, like my logins to sites where I have to register just to read an article), I figured the hardest part about converting would be retraining my fingers.
It turned out I had let IE save a lot more passwords than I’d thought. I haven’t been keeping formal count, but I’m pretty sure I’ve found over 30 so far, and I know I haven’t hit them all. Fortunately, I’d also recorded all the passwords in eWallet (in the Category I call “junk regs”), so it was just a matter of re-entering them all into Opera. But I was surprised - I would have thought I would have saved maybe 10 in IE. eWallet really saved me a lot of trouble on this one.
Why I like Opera - it seems to me a lot faster than IE7 and Firefox. I like tabbed browsing, and the built-in newsreader and RSS reader, but most of all, I like being able to search in my bookmarks, being able to pick “author mode” when I don’t like a page’s fonts and colors, and how configurable it is.
Why I don’t like it - it doesn’t support Web 2.0 very well, resized graphics look pretty awful, and I still end up surprised (at best) or puzzled (at worst) about where a window went or how to get back to one. But overall, it’s my current favorite. If you’re not happy with your current browser option, it’s definitely worth a look. Be sure you’ve got all your passwords, though!
(And, on an almost completely unrelated side-note, this preview is the funniest thing I’ve seen in a long time. The reason it’s slightly related is that probably only people who are familiar with the kind of opera that involves singing, classical music, and live performers will find it funny.)
And, yes, we will be fixing our site so it looks better in the newer browsers. And I’m hoping that we’ll be able to extend eWallet’s AutoPass feature to work in other browsers as well as the IE ones.
When I announced our open beta I promised that I’d let everyone know how it went. I mean this is a ‘behind the scenes at Ilium Software’ blog after all! I’ll start by saying that overall, this was a great experience. We got some really excellent insights into how people reacted to changes, caught a number of bugs, and found out how folks liked the new features. Without question I plan to run additional Open Betas in the future.
Statistics Here are a few statistics about the Open Beta:
Number of People Who Viewed the Page: 4000
Number of People Who Downloaded the Beta: 1500
Number of People Who emailed Comments: 28
Although I don’t have much to compare it to, this struck me as a pretty good response! Particularly considering how short a time the beta ran. While we didn’t get many email comments, what we did get proved very useful. Those 28 emails alone were worth the effort of setting this up!
A few more interesting statistics for you number crunchers out there:
Pocket PC Downloads: 912
Smartphone Downloads: 266
Palm OS Downloads: 172
Windows Only Downloads: 167
Duration What about the length? Well we knew from the start that this was going to be quick. In the future I’d like to run a longer open beta. One of the things we weighed was just how “beta” of a version we wanted to send out there. We’re sort of perfectionists over here and we hate to send out broken software. Still working on this one but I’m thinking at least three weeks next time. We’ll see!
Conclusions The conclusions I draw about the Open Beta in general is that I’m really glad we did it. Not sure that it would work for other developers but it certainly worked for us. My thanks to everyone who downloaded and especially to those that sent us comments!
Looking at the other numbers (the fact that Smartphone downloads well outnumbered Palm downloads for instance, when we have very strong sales for both platforms) leaves one wondering as well. Does it mean something? Is it a sign of use patterns? Or maybe Palm people are just less likely to try betas? Feel free to throw in your 2 cents! We’d be happy to hear it!