When the App Store opened, I dreamed of working for myself. After 26 years of service in academia and Corporate America I was tiring of enormous org charts and meaningless schedules. It took a little bit of time, but in late 2009 I finally quit my last day job. By then we had built up a little stable of apps, and the income was starting to pick up. I’ll never regret that decision, as many indie developers will tell you: once you work for yourself you’ll never want to go back to working for ‘the man’.

Year three on the App Store was an exciting one for us. Mundue apps have now been downloaded a total of 9.2 million times, about 95% of which are free apps. We released two new iOS apps this past year, and are working on a few more at the moment, and also created Mac and Android versions of reMovem. I gave a talk on ad network mediation at the Austin 360iDev conference, and met many new friends there and at other conferences. If you have the opportunity to attend the next 360iDev, this September in Denver, I highly recommend that you do so.

So what will year four be like? I’m very optimistic about the upcoming changes in iOS 5. With the sales of iOS devices still very strong, it looks like the next year or two will be even better for app developers. With over 400,000 apps in the store, the bad news is that your piece of the pie is constantly shrinking, but the good news is that the pie keeps growing ever larger with no slowdown in sight.

This post is part of iDevBlogADay, a group of indie iOS development blogs featuring two new posts per day. You can keep up with iDevBlogADay through the web site,RSS feed, or Twitter.

I rolled my own code to prompt users for a review and the results have been excellent. We’re now getting mostly 4 and 5 star ratings in the prompt-enabled apps. The key of course is in the timing of the prompts. I’ll explain a little about how the code works, then discuss the results so far. For a far better complete code template and explanation see also Noel Llopis’s blog post from last year.

Since the stated objective is to get positive feedback without annoying the user, we want to filter out people who have just launched the app for the first time. One way to do this would be to use a timer, maybe wait until some period of time has elapsed. That’s probably OK, but could lead to a prompt coming up at a truly random time. Instead I have code that checks for two things: time elapsed plus a new high score achieved. To detect a desired length of time, use something like this in your -[UIApplicationDelegate application:didFinishLaunchingWithOptions:] method:

if (![defaults objectForKey:kFirstRunKey]) {

    [defaults setObject:[NSDate date] forKey:kFirstRunKey];

}

This gives you the timestamp of the first run time. I typically define kFirstRunKey to include a unique version number, so I can record the first run of each update. Now each time a new high score (use whatever criteria you see fit) is achieved, check the current time against the first run timestamp, like this:

- (void) askToRateApp {

 if ( ![self reachable] )

   return;

 NSUserDefaults* defaults = [NSUserDefaults standardUserDefaults];

 if ( [defaults boolForKey:kAlreadyDeclinedToRateKey] )

   return;

 NSTimeInterval elapsed = [[NSDate date] timeIntervalSinceDate:[defaults objectForKey:kFirstRunKey]];

 if (elapsed < kAskDelaySeconds ) // approximately 1 day

   return;

Notice a couple of interesting things here. First, I have a Reachability test to exit early if there’s no connection. Second, if the user has previously declined to rate the app, respect that choice and do nothing. Finally, there is a test to see if enough time has elapsed. If not, again do nothing. At this point you could prompt the user, or optionally add more tests. Maybe you only want to prompt on the 17th high score. Then something like this would work:

 NSInteger showAsk = [defaults integerForKey:kShowAskToRateKey];

 // If showAsk is 0, the prompt screen will be shown.

 // If showAsk is > 0, we decrement it now.

 if ( showAsk == 0 ) {

   feedbackAlert = [[[UIAlertView alloc] initWithTitle:NSLocalizedString(@"AskToRateApp",@"") message:nil delegate:self cancelButtonTitle:NSLocalizedString(@"NoThanks",@"") otherButtonTitles:NSLocalizedString(@"RateNow",@""), NSLocalizedString(@"RemindLater",@""), nil] autorelease];

   [feedbackAlert show];

 } else {

   showAsk = (showAsk - 1) ;

   [defaults setInteger:showAsk forKey:kShowAskToRateKey];

 }

}

In this example, the showAsk variable is tested to see if the counter is zero. If it is, we show the feedback alert. Otherwise we decrement it and store it back in the default settings for next time. Set a reasonable initial value for kShowAskToRateKey. Once the saved value reaches zero, the alert will be shown exactly once. All that’s left to do is handle the buttons on the feedback alert.

- (void)alertView:(UIAlertView *)alertView clickedButtonAtIndex:(NSInteger)buttonIndex

{

  if ( alertView == feedbackAlert ) {

    NSUserDefaults* defaults = [NSUserDefaults standardUserDefaults];

    if ( buttonIndex == 0 ) {

      // No Thanks

      // Don't Ask Anymore

      [defaults setBool:YES forKey:kAlreadyDeclinedToRateKey];

    } else if ( buttonIndex == 1 ){

      // Rate Now...

      // and Don't Ask Anymore

      [defaults setBool:YES forKey:kAlreadyDeclinedToRateKey];

      [self showAppStoreReviewPage];

    } else if ( buttonIndex == 2 ) {

      // Remind Me Later

      [defaults setInteger:21 forKey:kShowAskToRateKey];

    }

    feedbackAlert = nil;

  }

}

For the “remind later” choice here, I’m resetting the kShowAskToRateKey to 21, but this can be any value you like. I recommend you use analytics or some other method to determine an appropriate measure of how much time is “later.” FInally you need a small piece of code to make the App Store review page show. This technique can be used on iPhone, iPod touch, iPad, and Mac, but on iPad and Mac it is not possible to go directly to the review page. You’ll go instead to the App description and may want to explain how to actually enter a rating or review in those cases.

- (void) showAppStoreReviewPage {

  [[UIApplication sharedApplication] openURL:[NSURL URLWithString:deepLinkReview]];

}

For the deepLinkReview you will specify the URL that takes users to the application’s review page on iTunes. It’s pretty straightforward to construct the URL manually. Justine Pratt wrote all about this on her blog last year. You can also wrap the URL in a LinkShare link if you are an iTunes affiliate.

So how well does it work? Like Noel I have see an improvement in reMovem ratings from 3.5 stars to 4.5 stars, with about twice as many written reviews per day as there were a year ago. Still, 2 out of 3 users choose not to leave reviews. Of the rest, half opt for the “remind later” choice while about 15% click the “rate now” button. I suspect only a percentage of those actually complete the process, but it’s better than none. It’s debatable whether this leads to more sales, but having more 4 and 5 star reviews certainly helps when people are looking at the App Store description. I also believe they use the number of reviews as a gauge to an app’s popularity, and, in turn, as a data point for their purchasing decision. So the more reviews, the better.

—-

This post is part of iDevBlogADay, a group of indie iOS development blogs featuring two new posts per day. You can keep up with iDevBlogADay through the web site, RSS feed, or Twitter.

Nevertheless, from the very beginning it was a pleasure to deal with the folks at Aptocore. The system they built was easy to integrate and manage, and the SDK had an excellent Xcode-integrated documentation set. The support team was knowledgeable and courteous, and always very professional. We’ll miss working  with them, and wish them well in their future endeavors.

Many developers used AGON in some interesting games. A few of my favorites were: Eyegore’s Eye Blast, Similis Deluxe, Sheepstacker, Popper, Inkvaders, SpringFling, and Azplode. Check ‘em out!

Full details on the new and improved MMTrackingController are on Github. Enjoy!

In the run-up to Christmas, ad spending goes through the roof. Ad-supported apps typically see their eCPM double and triple during this period, but not across all ad networks. That’s why it’s important to use a 3rd-party mediation layer to maximize your ad revenue. It’s interesting to pit the networks against each other, many promising campaigns of ultra-high returns (for an albeit short period). Being locked into a single ad network (even iAd) is not where you want to be during November and December.

Paid application developers struggle before Christmas with the onslaught of new& holiday apps, and daily price reductions designed to increase presence on the App Store. Why? Because Apple will sell 10 million new iOS devices in the current quarter. With a few million new users on Christmas day alone, being in the right place on the App Store will spell the difference between it being a big day and huge day. In 2008 our paid apps doubled in sales on Christmas and the week after. In 2009 that difference was closer to 4x. While it would be nice to see that again, I don’t expect it; but we’re doing everything we can to boost our apps’ positions.

Getting There

Recently we’ve written about raising prices and maintaining a steady-ish revenue. This works well under normal circumstances, but would probably relegate us to the lower levels of Christmas bumps. The games categories are just too competitive, there’s less perceived value in holding out at a higher price. In this case we want to time things such that a price reduction and other promotions conspire to give the highest rankings boost just before the 23rd. How come?

I’ll go out on a limb and speculate that most of our apps are purchased on-device. It’s just not that satisfying to buy apps on iTunes on your desktop computer. Unless you are drawn there from a review site or maybe a promo code, you’re probably spending most of your app-shopping time on the iPod touch or iPhone. And you’re a developer! Joe average citizen probably syncs his device  a couple times a month at most, and is not likely to wait around for iTunes to sync so he can enjoy a new purchase. If this is true, then the rankings on the App Store app on the device start to look very important. Especially that first “page” of 25 apps in each category. That’s where you want to be. That’s the magic page that will effectively boost your sales (free or paid) more so than being on the second or third page. Guess how many users never even tap on that “Twenty Five more…” button?

Final Thoughts

If you can get into that top 25, that’s great. Do what you need to do to stay there. If you’ve got truly awesome games, maybe a feature will help you along the way. I’m not that lucky. Advertising can help, some work better than others. We are trying out Tapjoy this year, and it looks very promising. Cross-promotion with other developers is also something we do throughout the year. Every little bit helps.

If you are in that sweet spot when Christmas arrives, you may choose to raise your price back to normal. This will certainly help your bottom line with the potential to reach millions of new customers in a very short time. Just remember to make that change before the 23rd, else you’ll be shut out of iTunes Connect and wondering what could have been.

—-

This post is part of iDevBlogADay, a group of indie iOS development blogs featuring two posts per day. You can keep up with iDevBlogADay through the web site, RSS feed, or Twitter.

Sales

With the tripling of the price the sales went down to 34.6% of the previous month. We didn’t change any other factors during this period, and kept up the usual amount of cross-promotion within the free version. Neither app was featured or advertised externally. During this time we faced an onslaught of new apps being featured and existing apps lowering their prices to gain a rise in rankings. That’s nothing new, but obviously can contribute to rankings fluctuations.

Revenue

Revenue has stayed extremely steady, in fact it’s up 3.3% in the October period shown. What’s immediately obvious is an increase in the daily volatility. There’s much wider swings from weekend to weekday. This seems to be the inverse of the sales drop change above, where the downloads fluctuate less at the lower rate. It would be interesting to compare this to other apps we have at different price points.

Top Paid Rankings

Rankings have been hit pretty hard. Red is Puzzle and green is Strategy. It seems safe to say they have dropped to 1/3 the previous month’s value, but my Majicrank data is unfortunately missing a few days. The rankings are important because they help to keep the app “visible” on the device, especially when the ranking is within that top 25. I figure the first page of apps in any category will contribute greatly, almost as much as a feature in some cases. For example, reMovem free is consistently in the top 25 for both Puzzle and Strategy, which drives enough downloads to sustain itself during periods of external pressure (paid-to-free and other promotions).

Top Grossing Rankings

Perhaps more telling (again, apologies for the spotty Majicrank data) is the top grossing ranks. This actually went up a bit, but has since dropped, though not nearly to the 1/3 level of the sales. Clearly, raising the price can lead to a sustained profitable rate. Of course, the downside to all this is: less users. In this era of “the power of free” where the goal is to get your app in as many hands as possible, we are not winning that battle. However, given that this is the paid part of the paid/free duo, and that we don’t yet have any lucrative IAP in either, this is OK.

—-

Over the past 28 months I’ve had 58 “Ready For Sale” emails from iTunes Store (I just counted). Even though 9 days sounds like a nice short time to wait, if you use it as an average review time, that’s 522 days for my 58 submissions. That’s about a year and a half. 522 days that you have to stage bug fixes and enhancements, work on other projects, hold your breath, and cross your fingers. It seems like a bit of a waste of time doesn’t it?

The system appears broken. Rather than attempt to fix the problem with lengthening review times, Apple has tweaked the status history to make it feel like the process has been improved somehow. Remember how the binary was uploaded and sat there for days, then got reviewed and approved pretty much within hours (figure 1)?

This doesn’t seem to be the case anymore. Nowadays your app is more than likely to go straight into “In Review” and sit there for a week or more. Did the process that took hours previously become one that takes days now? Seriously? (figure 2)

Given that the process is still basically a black box, we can only conclude that there’s an emphasis at Apple to get the updates into “In Review” state regardless of when they will eventually get reviewed. Maybe this helps with their stated review status percentages on the  Developer News and Announcements site. Perhaps it would be more helpful to show the average review times instead?

As for my apps, the last few had overall submission->approved times of 9 days, 10 days, 8 days, 11 days, and 8 days. That’s an average of 9.2 days, so my email today came right on schedule, it turns out. I should have planned for it. Today’s update? It’s for the free iPad app reMovem 2, and it includes iOS 4.2 compatibility (hope you are thinking about that) and 2 cool new themes designed by Mike Berg of @weheartgames fame. Please check it out on iTunes or the web.

I’d love to hear from other developers with their submit-wait-suffer-approved tales. Are my wait times average or out of whack with your experiences?

—-

In the case of reMovem, not much. This app has never been featured but maintains a top-100 ranking in the Puzzle and Strategy categories for much of the last two years. There’s a significant upsell through the immensely popular free version, and any app that can snag a spot in the top 100 of any chart will attract a certain amount of traction. Reason? There are four “pages” of 25 apps that a user can see when perusing the App Store on an iPhone. This is the poor man’s feature, but it comes at a cost.

If your app is not one of the perennial favorites or currently featured somewhere by Apple you will need a low price just to crack a top 100 ranking. At $0.99 reMovem was very consistently in the 25-40 range for both Puzzle and Strategy (figure 1).

reMovem seemed stuck at around #25, and there was no more leeway with the price, other than going free. We tried http://freeappaday.com/ in May and don’t want to do that again. Besides, with the regular free version, and a free Halloween version (and an upcoming free Christmas version), it seemed like a good time to differentiate more on price. It’s likely the price will go back down during the holiday feeding frenzy, but for now we hiked the price to $2.99. So, at 3 times the previous price, do sales fall to 1/3? Not quite (figure 2).

Here’s where things get interesting. Though sales seem to plummet, they bounce back a bit. Although it’s too soon to say, there’s hope that the daily download will stabilize at a number above 1/3 the old number of downloads. This is great for the bottom line (revenue) which appears to be holding up nicely (figure 3).

So in the short term, raising the price appears to boost the bottom line, at least in this instance. I think the new price is important, too. In the past we’ve juggled with a price between $0.99 and $3.99, all with different results. If you double the price you’ll see a similar drop-off to what we have illustrated here, but perhaps not much of a change in revenue. Perhaps a follow-up post will chronicle how this change pans out over the next few weeks.

Far more interesting is the effect of ranking. As you can see (figure 4) the rankings have taken a beating, but they’re still somewhere in the top 100. After falling to around 80 and stabilizing things seem to be in good shape. My fear was it would drop like a rock right off the charts. Usually we control the price to keep the app in the top 100, but it’s not entirely predictable. Also, not shown, the top grossing ranks have edged up slightly to near 50. These metrics may take more time to adjust, as they consider more than raw sales x price calculations.

I had been fearing a spate of negative reviews over the price change, but so far only 4 and 5 star ratings continue. I heard somewhere that if nobody complains about the price you aren’t charging enough. Users that pay more for a product are more attached to that product and more likely to give it a good rating to justify their expense. A cheaper product lowers the barrier to complaints. Plus, we’ve been heavily promoting the prior “special” low price, so there are no excuses for those that waited, only regrets.

What we learned from this exercise is that:

• raising the price can hurt sales (but not kill them)
• raising the price enough can overcome lost sales in revenue
• raising the price can seriously hurt rankings (but not kill them)

It’s way to early too draw serious conclusions from this experience, but we now have the wiggle room to lower the price again at a convenient time. This could be to coincide with an update, or to counteract any massive price drops elsewhere. We’ll see. It’s nice to have options.

—-

Keeping customers happy means more than just adding features or putting games on sale occasionally. Noel’s iDevBlogADay post last week about communicating with users got me to thinking. I’m not doing a great job of communicating with users, but it’s not all bad news. If you’re like me, you get many emails a week about some aspect of your product(s) from users. It’s tempting to dismiss the complaints, and developers know you can’t please everyone. But I’ve been working on “taking the high road,” and it seems to generally pay off.

What does this mean? I’ve written about recent product changes and how the users react to them. I think in general there are far more players who like the changes than those who don’t, and we have metrics to validate that. People that respond to the prompt to rate/review an app are usually going to have good things to say. A few will spontaneously write bad reviews or leave the dreaded 1-star rating. I no longer lose (much) sleep over the latter, but when someone bothers to send a support email, I take it very seriously.

I’m not promising an instant reply. Other developers, even friends of mine, sometime take weeks to reply. I’ll usually get to it in a day or two. All the support emails typically fall into similar buckets that are easy to respond to.

“Can’t get it to run.”

“How do you play the game?”

“I liked it better the old way…”

These folks are typically happy with a simple explanation or offer of appeasement (promo codes work great!). Once in a while we’ll see an email from a truly angry user. If you handle these properly you can turn lemons into lemonade. This is where it pays to take the high road. Using a common sense approach will almost always work in your favor. Be respectful, be sincere, be accommodating wherever possible. If someone with an issue sees you being responsive they may very well change their opinion and even reverse a bad review or rating. I’ve seen this happen a number of times.

All it takes is patience. Here are a couple of examples of unhappy users who changed their minds. One guy wrote this email about our iPad game:

Subject: reMovem with ads sucks

I paid for this app, not the advertising.

What’s up with that? reMovem 2 is a free app. My response:

Hi Bob, [not his real name]

reMovem 2 for iPad is free and always has been free. If you look at your receipt from Apple iTunes Store it shows a price of “free.” I use ads in my free apps and have never used ads in any of my paid apps.

In the future we may add an option to opt-out of ads with In App Purchase for reMovem 2.

It is frustrating as a developer to get bad ratings when they are undeserved. I do appreciate you writing to me so we could straighten this out.

Thanks,

-Matt

I’m in the habit of using my name in support emails so folks know there’s a real person here. This generally leads to a more civil discourse. I also want to acknowledge the effort he took to write to us instead of just leaving a bad review. In this case, Bob was appreciative even though he stuck to his guns:

Matt,

Then it’s my mistake and I apologize for the misunderstanding. I do own the purchased iPhone version. reMovem is one of my favorite apps and it was one of the first apps I downloaded for the iPad. When I wrote to you, I assumed that had I paid for the iPad version, too.

The take-away is that there are people willing to pay for the app and avoid the ads. The other take-away is that I “reMove-d-em” from my iPad and will not reinstall it until there is an ad-free version.

I really appreciated you response.

Thanks.

Bob

Now we can agree to disagree, but I know that Bob is a loyal customer and have an idea of how to make him a repeat customer in the future. Win!

Here’s another example of someone who’s not happy with Apple’s spartan Game Center signin screen:

I paid for this app to avoid annoying interruptions but get a stupid popup asking me to logon or create an account. I don’t want to do either but tapping cancel only gives me temporary relief. I get this popup several times each game. I will not be buying any more software from this company.

Sent from my iPhone 4

Doesn’t look good. My response:

Hi Joe, [again, not his real name]

Thanks for taking the time to write to us about reMovem. The “stupid popup” is for Apple’s Game Center feature, which lets us use online high score leaderboards. We wish Apple had a better interface too, but this is what we are stuck with at the moment. Chances are more of the games you like and use will support Game Center in the near future. For more information:

http://www.apple.com/iphone/features/game-center.html

In any case, it is very easy to turn off the Game Center features:

1. Go to the Info screen and turn off the Game Center switch at the bottom.

2. Quit and restart the game.

Note: On an iPhone 4, quitting requires more than just pressing the Home button. Let me know if you need further assistance.

Thanks,

-Matt

Joe was also appreciative of my response and can now play the game he likes:

I apologize for blaming the popup on your application. I have not seen it anywhere else. I turned it off and now it plays without interruption. Thank you for your help.

There are many other examples, and this is not exactly rocket science, but I think you get the point. Treat the customers with respect, even the angry and combative ones, and they will respond in kind. These are the kind of users that will remember you made an effort to reach out to them. I don’t think Bob or Joe expected me to reply at all. But since they took the time to write, why not do my best to make them happy?

Take the high road, yeah!

—-

This post is part of iDevBlogADay, a group of indie iOS development blogs featuring two posts per day. You can keep up with iDevBlogADay through the web site, RSS feed, or Twitter.

Background

The motivation behind most updates is to add features or otherwise enhance an app in order to attract new users or retain existing ones. If you’re using 3rd-party software such as OpenFeint, ad networks, or game frameworks, you need to frequently update for those as well. Compatibility with the latest iOS version or iDevice du jour is pretty important, too. Here at Mundue HQ we’ve got a big pile of devices and a testing matrix that would make your eyes glaze over. Deciding whether or not to support older devices is a tough choice all developers must make, and having analytics in your code can help.

Earlier this summer we added rudimentary support for iOS 4.0 to some of our apps. This was not strictly required, but I think the fast app switching is a big win for the user (improves perceived responsiveness of the device) and the more core Apple functionality you can support, well, the better off you’ll be. The one thing that was still missing from our reMovem games was the “hi res” graphics designed for the Retina Display devices. Initially just the iPhone 4, this now includes the new iPod touch 4th gen., which will be very popular come Christmas, I’m sure.

On September 2 we finally found out that Game Center would be available with the (then) upcoming iOS 4.1 release. This presented a compelling reason to add it to the updates we were already working on. Until then, Game Center was just promised for “later this year.” So we worked out a plan to modify some apps to include Game Center and all of them to include “hi res” graphics. We had already been working with the artist to update graphics, so the timing couldn’t be better.

Feedback

Fast-forward 4 weeks and approximately 1,275,000 downloaded updates later, and there are two main areas users complained about. Yes, the “hi res” graphics and the Game Center support. For games like ours which are neither serialized nor completion-based, replayability is crucial. It’s easy to see how users are trained to expect ( demand, even ) regular updates for some games, but to be honest we don’t get too many requests for specific features. So how could things go so badly, or did they? That’s why it’s so important to keep things in perspective.

Reviews are a good measure of satisfaction, and by adding a time-delayed prompt to rate the app you can ensure decent reviews from happy customers. This is easily accomplished by prompting people who have shown they appreciate the game, preferably when they are in a good mood, like after reaching a level or making a high score. If you look at the ratings alone, then we should be happy with reMovem’s 4.5 stars and reMovem free’s 4.2 stars (as of 9/28/2010).  But let’s look at each of the problem areas in a little more detail.

Colors

You would not believe the number of people complaining about a slight change of colors! “Hurts my eyes,” “Ugly Update!,” “Can’t play any more” are just a few of the comments received. Granted my vision is not that great. But I’m not colorblind, just very nearsighted. Still, the colors look good, especially when seen on the Retina Display. The original purple color was too blue, so we modified it to be actual purple, but most assumed it was blue. Aside from that we replaced a rarely-used fifth color (pink) with blue, to better match the existing icons.

At first it was only complaints about the colors. Not a single mention of the improved “hi res” display. I forgot to mention that with iOS 4.1 Apple fixed the issue with named image resources, so that the @2x images are properly used. You can clearly see the difference in these actual-size screen grabs.

In any case we began to worry that there was actually something wrong with the images. It’s so easy to overreact to early feedback. I knew it would take a couple of days for the delayed review prompts to kick in. Fortunately that happened, and after an initial wave of complaints about the colors, the true fans started writing good reviews and leaving mostly 4 and 5 start ratings.

Game Center

Game Center is interesting, because the ones that complain are so adamant about it. The best is “Game Centre integration has spoilt this app.” Come on, really? The Game Center integration is optional with a big giant “Use Game Center” switch on the settings page. I know that Game Center is flakey in its initial release, and Apple could’ve made the sign-in screen less generic, but it’s not really that bad. Other classic complaints are “I don’t want to keep track of scores,” and “How do I shut off the login junk?”

I think the Game Center fuss will die down when players realize that more of their games support it. I reply with a gentle reminder to that effect, and point them to the Apple page which describes its benefits. So far nearly 6,000 players have entered high scores. That’s only a 3% adoption rate, but we haven’t tried to compute how many players there are on capable devices.

Conclusion?

Is it time to panic? No. When you upgrade any app you will most definitely catch some flak from a vocal minority who dislike any changes. In time the majority of users will rally with good reviews and ratings. As my friend Markus said, “that problem will solve itself by pure mass distribution.” I couldn’t agree more. Be patient, wear a thick skin, and remember to prompt the happy users to rate your apps.

This post is part of iDevBlogADay, a group of indie iOS development blogs featuring two posts per day. You can keep up with iDevBlogADay through the web site, RSS feed, or Twitter.