Wednesday, May 4, 2011
Wednesday, July 7, 2010
Friday, June 25, 2010
I was curious about how the iPad plans that were announced by Bell, Rogers and Telus compared, where the break points were, and so forth. So I threw together a Google Spreadsheet to do some quick math on the plans. Assuming I read the plan rules correctly, I think the lessons are as follows:
- Bell and Rogers have eerily similar plans, like one copied the other, or both took a suggestion from Apple.
- The $15 plan offered by Bell and Rogers saves $5 over the $20 plan from Telus until you use more than 250MB.
- Telus' one-price plus overage model is cheaper than Bell and Rogers' $35 plan from 250MB-800MB.
- From 800MB to 5GB, Bell and Rogers $35 plan seems to be the way to go, because you'll be paying more than $35 by the time you pay Telus for your overage.
- After 5GB, it seems like Telus' plan, which maxes out at $50, would be cheaper than paying Rogers or Bell for another $35/5GB, assuming Telus doesn't cut you off.
- Telus does have fine print saying "Subject to a monthly data limit of 5GB", but they're not very clear what happens if you hit that limit.
- Neither Rogers nor Bell explains what happens when you reach your cutoff. If you run out of data on the $15 plan, can you upgrade to the $35 plan for $20, keeping the original timeframe? Can you buy a new 30-day window of $15?
Wednesday, June 16, 2010
Marco Arment on iPhone Multitasking:
One of my most common feature requests is for Instapaper to periodically download articles in the background. A lot of people forget to launch the app to let it download content before going underground or boarding a plane.
I’ve already received multiple emails from people who are excited for iOS 4’s multitasking because they can’t wait for this to finally stop being an issue, because they think Instapaper will be able to download articles periodically in the background.
It’s painful to respond, crushing their hopes, to tell them that the iOS multitasking system doesn’t allow me to do that.
The solution he proposes:
- The application gives the system an NSURLRequest and an ideal refresh interval, such as every 30 minutes, every few hours, or every day.
- iOS executes that request, whenever it deems that it should, and saves the response to a local file.
- Next time the application launches, iOS hands it an NSData of the most recent response.