Awkward Silence

Verizon Subsidized Unsubsidized iPhone 5

Tom — Mon, 24 Sep 2012 21:51:09 +0000

I currently have the Verizon Family Plan with 1 iPhone 4 and 2 basic phones for the kids. They love them and don’t need smart phones (yet). Our usage is like this (averaged over 6 months):

130 minutes talk
1800 texts (did I mention they’re two teenage girls?)
50 MB data

We share 700 minutes talk and have unlimited texting. I have a grandfathered unlimited data plan, which I obviously don’t use much. Most of my data usage is over wifi at home. However, I wonder how much that might increase with LTE speeds.

In order to get a subsidized iPhone 5 I would have to make two changes to my plan:

Switch to a Share Everything plan
Drop the unlimited data

Quite honestly I would drop the data. Whatever Verizon. But here’s the sticky bit. Moving from the Family Plan to Share Everything with the lowest amount of ‘shared’ features will cost me $30 per month more. And this won’t buy us anything new. The kids won’t use any shared data. We’ll have unlimited minutes, of which we’ll still use about 130. If we do move the kids to smartphones, that’s another $40 per month each.

So… If I buy an iPhone at retail, I can keep our plan as-is. The upfront cost is $650 (using the 16 GB for comparison) and over the course of two years, I would come out about $400 ahead (whichever model I choose). And, I wouldn’t be under contract. Disincentivized much?

I don’t know about the long term, but right now buying the unsubsidized iPhone 5 and taking the $400 savings from Verizon seems like the way to go. I suspect at some point something will tip me to needing to change my plan and they’ll nab me. I just hope by then one or more of the pre-paid carriers are ready to step in and get some business.

Disclosure Indicator or Detail Disclosure

Tom — Wed, 07 Mar 2012 05:31:22 +0000

I’ll post this just to show how wet I am behind the ears… When setting up a bunch of TableViews for lists and detail views, I came to need both the Disclosure Indicator and the Detail Disclosure. I understand when one is used vs. the other, but wasn’t familiar with working with them in code.

The long and short of it is, the Disclosure Indicator is pure eye candy. There is no callback, no way to create an IBAction for it (even if you press the control key really hard…) nothing. You just handle the row taps like any other:

tableView: didSelectRowAtIndexPath:

Detail Disclosure gets a shiny action all it’s own, built in to every NSTableViewController as part of the delegate:

tableView: accessoryButtonTappedForRowWithIndexPath:

I guess the 3d look of the Detail Disclosure vs. the flat Disclosure Indicator is a clue, but sadly it was lost on me for too long as I was working through so much else.

Fresh Start

Tom — Wed, 07 Mar 2012 05:08:45 +0000

After having my old site hacked and blacklisted, I decided the most expedient cure was the old slash and burn. I may try to recover the old posts from a db backup, but since the, ahem, newest, was over a year old, I don’t see a lot of value in spending the time.

If you’ve still got me in your RSS from my RoR days, you may want to change channels. I may post occasionally on RoR, but mostly for now anyway, the topics will revolve around iOS. After several fruitless years in the Apple Developer program, I finally got off my duff and started an app for real. It’s been great, and I’m looking to post some notes on things I’ve sorted out along the way.

There’s already a ton of great documentation (thanks SO!) but sometimes it seems I have to assimilate a multitude of notes to patch together a solution. I’m looking at you, DatePicker, NSDate/NSTimeZone/NSCalendarComponents and Core Data and NSPredicate…