Thursday, February 02, 2012

Netflix is my new HBO

 When I grew up in the 80s, a particularly life changing event was when my family subscribed to HBO.

There were no parental controls in those days. If you had parents like mine that put a TV in your room with HBO on it, you could watch all sorts of stuff that you had no business seeing. HBO's always had loads of cheap crappy movies to round out the expensive good stuff and original series. HBO would play those crappy movies over and over, I'd watch'em over and over again. The later at night the better, especially if it was some horror or mind fuck flick. Past midnight, I'd watch stuff that I'd never give time during the day. Nightmare on Elm Street 4? Why not, I've got time. Swamp Thing? I've only seen it 15 times, what's one more viewing.

It hit me tonight that Netflix is my new HBO. Insomnia at 3 AM? Why not Don't Look Back, subtitled because it's French, starring The Matrix Reloaded's Monica Bellucci and The World Is Not Enough's Sophie Marceau? I've got nothing better to do.

The perfect kind of late night crappy movie is the one you:

  • Can fall asleep to if you get tired again
  • Don't mind turning off at any point because you really don't care about the story
  • Might show you a bit of skin, no matter how fleeting
  • Is unintentionally funny, so you laugh at it not with it
  • You can watch in the background while you do something else (like write this post)

Plus, Netflix has mostly crappy content and it's getting worse as movie studios refuse to cut deals for newer better streaming content in reasonable timeframes. Which makes Netflix kind of perversely perfect for my late night insomnia needs. I won't be turning it off again if it stays anywhere close to $8/month and keeps the obscure content and/or bad content. And to think, I haven't even entered the time wasteland of TV-MA rated Japanese anime yet!

Wednesday, February 01, 2012

Exhibit A. On Why iOS 5 Newstand Apps Should Always Be Universal

I've had the New York Times app on my iPad since Newstand launched alongside iOS 5. I don't read the content, it's just not part of my workflow. What I love however are the notifications of important events just for having the app installed. The editorial selection is perfect, so I downloaded the NY Times app to my iPhone to get the notifications there as well.

I didn't realize what I downloaded on the iPhone was not a universal app. Imagine my surprise when I got back to my iPad & through the magic of App Store automatic downloads it appears I now have two NY Times!

When the iPad first came out, I would've agreed it was acceptable to ship separate apps for one actual app to pay for the cost of adding iPad features. No more. A universal app is really just table stakes at this point  There's no user experience case to be made for shipping separate iPhone & iPad apps. Multiple apps for the same app just creates user confusion on the App Store, and in cases like this, on the device as well.

And it just looks really dumb in Newstand!

Why External Links Should Maybe Open in New Tabs

UX Movement posted Why External Links Should Open in New Tabs. I've never quibbled with any of Anthony Tseng's advice before, but this time I think he misses the mark somewhat.

True, for the primarily audience of this blog, I think opening external links in a new tab makes sense. I just went back to my posts this year and changed all external links. That's the key though, this decision has to be made based on the audience of the site.

Ever watch an older user or even young but not to savy user get dumped into a new browser tab? This sentence from UX Movement completely applies:

When a new window opens, it covers the user’s earlier window. The user is left confused and wondering how to get back.

Just replace window with tab and it still applies. All these users know is the back button.

So if your trying to appeal to browser savy users, go ahead and open external links in a new tab. If however you're trying to appeal to a broader audience with less browser know how, open external links in the current window or tab.

Tuesday, January 24, 2012

Apple: This Hard to Find Evidence Suggests You Should Release iBooks for Mac OS X

Top Free in the Mac App Store
Look at the image on the left of the Top Free apps in the Mac App Store. Notice anything?

Number 1 with a bullet is iBooks Author. Look further down. Number 5 is Kindle. That's like oil and water. You know what would be nice to have as Number 1 or Number 2. iBooks! iBooks Author and iBooks are two tastes that taste great together.

I can think of reasons why Apple might not release iBooks for Mac OS X, but none of them make much sense to me. If Apple wants to take on Amazon and Kindle for eBook supremacy, they have to broaden the reading platform off of just iOS.

I would have bet real money that iBooks for at least Mac OS X was going to be released at the Education event. Clearly I would have lost big.

I'd like to be able to read iBooks on Mac OS X, even if it's just for the occasional reference. Clearly the Mac App Store proves Kindle book readers aren't just reading on their Kindles.

This is What's Wrong with Hollywood: Where are the biggest box office movies (not) streaming?

Take a look at this compilation of the Top 100 movies of 2011 and where they are available (or not) to legally stream from online. This isn't even a complete list as the studios still frequently will only put the standard definition version of a movie up on iTunes when of course an HD copy is available. Also, support for iTunes Extras is nonexistent or weak.

This is why Hollywood is losing money to piracy. There will always be people that just don't want to pay for content, but the big attraction of piracy to honest people is that it feels like everything is available. It's a better service. Seems very analogous to Napster before Apple convinced the music labels to license a very high percentage of their catalogs at reasonable prices for download. Then you have the studios trying to launch their own streaming service, while continuing to cripple the established services out there.

Hollywood has crippled the legal download sites with this quagmire of availability, SD vs. HD, and little to no price break over buying a manufactured physical disc. Clearly the studios are trying to preserve buying physical discs or make at the least make it more enticing than downloading, but it's just not going to happen anymore. The tide has turned. Add to that the complicated "windowing" that studios try to enforce on home viewing rights, and a lot of consumers just check out.

This should be obvious, but don't the studios get that most people can't and won't keep track of the studios windowing schedule? Once you market a movie, if people want to watch that movie and they can't get it legally and at a fair price, at some point they are probably going to investigate pirating because it bypasses all the studio bullshit.

I'm not supporting pirating, but it's not hard to understand the appeal beyond just not paying for stuff.

Update
I tried to watch Game of Thrones and this is what happened cartoon from The Oatmeal perfectly captures the problem.

Update x2
Andy Ihnatko perfectly captures what I generally try to practice regarding the byzantine content access rules, find something else to do!

Friday, January 13, 2012

Thoughts on 44 days of uptime in Mac OS X 10.7 Lion

Decided going into the Martin Luther King, Jr. Day weekend I would actually shutdown day job MacBook Pro instead of sleeping it like I had every other day for who knows how long. I only thought of doing this to save a battery charge & discharge cycle.

I wondered: "How long have I been running this instance of OS X 10.7 Lion?"

44 days was the answer Terminal command uptime gave. The MacBook Pro hadn't booted since November 30, 2011, a whole other year ago! Probably the last time I had powered it off because of Thanksgiving break.

I was kind of shocked for two reasons. I'm usually doing every 2 week beta OS updates or standard updates that require reboots. I skipped the current round because I really wanted to run stable after the OS X 10.7 Lion, Xcode 4.x, iOS 5 beta trifecta over the summer & fall. More surprising though, rebooting OS X has been completely deprecated in my mind as a useful activity unless forced to. To be fair of course, I've quit cycled a few heavy use apps (here's looking at you Xcode) over this stretch. But the system has remained perfectly usable and stable. If not for the holiday, I would have just slept the Mac like I had done before.

What a contrast to the issue I have with Windows 7 on my iMac that would have necessitated some task killing after a few hours if I was really using the OS day to day.

What I'm really curios about is iOS device uptime. I don't ever turn off or reboot my iPhone or iPad except to install a software update.

I marvel at the software engineering!

Wednesday, January 11, 2012

iOS 5 Dev Warning: UITableView's Multiple Select During Editing Doesn't Work with Swipe to Delete

I attended Session 125 - UITableView Changes, Tips, Tricks at WWDC 2011. I also downloaded the video & slides of that session from the WWDC 2011 Session Videos site  (Apple developer account required) .

You can here it in the video, and being in the room, one of the, if not the, favorite moment for developers at the talk was when multiple select during editing was announced. The announcement starts at 16:51 in the talk video.

Jason Beaver immediately shows Apple's Mail application in edit mode. Why? Because that's what every developer and user that has spent any time in Mail want in their apps when editing lists of user content. 

You would expect, given the heavy references to the Mail app and how it works that what regular developers would now have in UITableView is exactly the functionality Mail supports.

But You Would Be Wrong Because Swipe to Delete is Disabled!
If you do this in your code:

self.tableView.allowsMultipleSelectionDuringEditing = YES;
or change the UITableView property in the XIB for Editing to use Multiple Selection During Editing you don't get swipe to delete.

I have no idea if that functionality was planned at WWDC and got dropped during development. The only hint you get swipe to delete won't work in the iOS 5 release documentation is the following on the allowsMultipleSelectionDuringEditing property (emphasis mine):
The default value of this property is NO. If you it to YES, check marks appear next to selected rows in editing mode. In addition, UITableView does not query for editing styles when it goes into editing mode. If you call indexPathsForSelectedRows, you can get the index paths that identify the selected rows.
So if you don't see the docs, or it just doesn't click on first read that this means no swipe to delete, you might do a whole bunch of work for no reason because you need both multiple select during edit and swipe to delete, just...like...Mail.app. I'm only saying this for a friend, of course.

Skeptical? I was too, went through all 7 stages of grief before conclusively proving it. I kept thinking: How could Apple play Lucy with the multiple select football to my Charlie Brown?

Prove it to yourself. Go download Apple's TableMultiSelect sample (Apple developer account required). Open MyTableViewController.m and paste the following three lines in (I pasted after the tableView:cellForRowAtIndexPath: method just to be tidy):

// Override to support conditional editing of the table view.

- (BOOL)tableView:(UITableView *)tableView canEditRowAtIndexPath:(NSIndexPath *)indexPath
{
    return YES;
}


- (UITableViewCellEditingStyle)tableView:(UITableView *)tableView editingStyleForRowAtIndexPath:(NSIndexPath *)indexPath 
    return UITableViewCellEditingStyleDelete;
}

- (void)tableView:(UITableView *)tableView commitEditingStyle:(UITableViewCellEditingStyle)editingStyle forRowAtIndexPath:(NSIndexPath *)indexPath 
{
    NSLog(@"Commit Editing Style");
}

Run your app in the simulator and true to swipe to delete. It won't work.


Now go to line 74 and comment self.tableView.allowsMultipleSelectionDuringEditing = YES; 


BOOM, you got swipe to delete!


Next Steps
I know, file a radar or GTFO and I will, eventually. I say this not to deride Apple. UITableView is a great piece of UI programming. Whenever designing something of my own, I always ask:
What Would UITableView Do?
I wrote this to warn developers using UITableView's multiple selection functionality at the time of this writing (Xcode 4.2.1 & iOS 5.0.1) is an either or choice with swipe to delete that user's are most likely not going to be happy with. Better to stick with custom implementations unless/until Apple changes the functionality.


Update
An workaround has been found. Default your tableView to not allow multiple select during editing so you get swipe to delete. Then in your viewController's setEditing: method, enable multiple select on your tableView. When editing is done, set your tableView back to not allow multiple select during editing.


Seems like a hack, but I've had a bunch of people tell me it works!

Monday, January 09, 2012

Integrating SharePoint with Twitter on a Corporate Intranet

Thankfully I don't have to know how to integrate SharePoint with anything right now, but if I did, I'd know who to turn to for insight.

 

John DeGiglio is one of the smartest people I know, and one of the most relentless developers I've ever seen. If you give him a problem, he will solve it. John and I used to write .Net apps together, and he specialized in  SharePoint. He's become an expert over the last 5 or so years.

John's recently published his first public blog articles and CodePlex projects on integrating Twitter with SharePoint.  

Twitter Displays Tweets WebPart

How this WebPart came together is documented in two blog posts hosted by Synergy Online:

Displaying Tweets on your Corparate Intranet - Part 1
Displaying Tweets on your Corparate Intranet - Part 2

John's also restarted his blog Backhand Volley at DeGiglio.biz. Unfortunately some good content was lost when Microsoft shutdown MSN/Windows Live Spaces. He didn't get the notification from MS to download his content before it was deleted.

John's also on Twitter @jdegiglio and his Tweets just went public! I expect more SharePoint or tennis focused tweets, John's a huge tennis fan.

Saturday, December 31, 2011

Retro Review: Mass Effect 2. Why Can't I Play Like Captain Kirk?

I finished Mass Effect 2 around June 2011. I played the game from the start with several pieces of DLC installed on the Xbox 360. I didn't have "Lair of the Shadow Broker" installed, nor did I ever get it. Overall, this was a very good game. I look forward to playing Mass Effect 3 in early 2012. 

The good parts of Mass Effect 2 were great. Voice acting is fantastic. Combat was streamlined from Mass Effect 1 making it excellent. The RPG part was also streamlined, eliminating a lot of the busywork from ME1 without losing the customizability.

What I expect from the Mass Effect series is an adult science fiction game. Why then is Commander Shepard limited to such puritanical sexual relationships? I want to play my Commander Shepard like Captain Kirk, sleeping with every available crew member or mission encountered alien that I can! Instead, what I get in Mass Effect is a very linear and monogamous relationship system only on ship were all the potential romantic participants are apparently talking to each other. It's just like High School. Downloadable character Kasumi's only ship function appears to be relationship gossip. The main characters all never appear to leave their assigned ship rooms, yet everyone knows everybody's business! Other than Kelly, all other characters are prudes. If I had to hear Jacob Taylor say "Let's not push it, we got a good thing going here Shepard" one more time, I would've thrown my controller at the Xbox. The system is to on rails.

What I would do if I were designing the game is to leave all sexual relationship options available at all times, just make those decisions tie to paragon/renegade points. If Shepard has already started sleeping with a character, and then tried to pick up another lover, that choice could feed into the complexity of your character more completely. Play with the highest honor on the battlefield, but be a total dog with your crew, or vice versa. I even have a problem assigning renegade points to a Shepard that sleeps around, but within the design of the game doing that would be the cleanest "fix". Also each character could have different relationship needs to achieve their highest morale. In ME2, all potential romantic characters appear to have the same end need, a monogamous relationship with Shepard. Again, Kelly excepted, but even she won't continue or start a relationship with Shepard if Shepard has already started something with another character, and she's the "slut" of the ship.

I look forward to the day when I can play as a character in a game that was as open as Captain Kirk over 40 years ago.

Friday, December 23, 2011

How I Came to Loathe the Nintendo Wii, and it's Microsoft's Fault!

I loved the Nintendo Wii when I got it back in 2007. When I looked up my review, I couldn't believe it had been over 4 years already. LIke pretty much everyone, I played Super Mario Galaxy & thought that was great too. My family had a lot of fun with Wii Sports and Wii Sports Resort over the years. Slowly but surely, my initial love for Nintendo's console grew to dislike, then outright loathing. There wasn't a moment of clarity when I realized I never wanted to use the Wii again. It was a gradual process and it was Microsoft's fault!

After a few years with thr Wii, I was completely over the four part Wii controllers: remote, nun-chuck, rubber bumper, and motion plus. The batteries for the remotes were never charged. The nun-chuck wire always got tangled. The rubber bumpers to make sure you didn't kill someone flailing around we're never in the configuration you needed to play what you wanted to. Worse, no one but me, not the kids and not the wife, could untangle the whole mess. The fact that Nintendo didn't ship the controllers as rechargeable became a deal breaker, even though I was using rechargeable batteries. 

I couldn't pin down what i didnt like about thr Wii until I first heard about the Kinect. A bit flipped in my head right then that I was done with the Wii if Microsoft didn't mess it up. I didnt want to use a controller for motion controls ever again. Amazingly, Microsoft got it right, not perfect, but good enough from all the stuff I read. I didn't rush out to buy Kinect. I waited for a while to get some more life out of the replacement Xbox 360 I got from the Red Ring of Death fiasco. That I even considered giving Microsoft more money was amazing, they were all but dead to me before Kinect was announced. Going back to Microsoft was also given a boost by Sony announcing their Wii competitor, Move, packing its own fleet or wand/remote controllers. 

The announcement of the Nintendo Wii U and Sony's PlayStation Network security breach happened within a few weeks of each other in May/June 2011. Those events were the tipping point to Kinect for me. Wii U looks ridiculous. I normally hold out on judging a product until release, but I couldn't suppress an immediate reaction of disappointment. Wii U looks like an iPad and Apple TV using AirPlay, but without a good digital download store. Sony's ridiculous lack of network penetration testing and basic security controls were inexcusable. 

By August I had sold my Wii and replacement Xbox 360 at a yard sale to finance the purchase of a new Xbox with Kinect. I was going to sell the PlayStation 3 as well, but Uncharted 3 and a few unripped Blu-rays have caused a delay.

As for the Kinect itself, pretty awesome. Demonstrably better than the Wii for exercise games, which I've used but my wife really enjoys. And in extended Kinect Adventures sessions, no Wii remote like cramping or fatigue, just normal exercise pains. Having the ability to video chat is nice too, though it is odd that it isn't in HD. With Christmas days away, a bunch more Kinect titles are coming home, I'm sure the whole family is going to be having a lot of fun.