Thursday, May 26, 2016

Fixing the Apple TV with Instant Apps

The Apple TV is already a pretty great platform. Hopefully it will become even better this year.

Many Apple TV apps require a companion iOS app. My friend wrote a great trivia game for up to four players. Each player must use an iOS app to play the game. Trivia questions are displayed on the TV and players race to select their answers using the companion iOS app. The need to find and install the companion iOS app in the App Store is a significant source of friction. It is also a nuisance to have a companion app icon cluttering up your home screen when the app is only useful while playing the Apple TV game.

A few months ago I had an idea to improve this situation. My idea was to give developers the ability to write iOS extensions to tvOS apps. These extensions could install and run automatically within the Remote app on an iOS device. Basically, the Remote app would double as a container to run these tvOS app extensions. This would enable the Remote app to morph into whatever it needs to be based on the app that is currently running on the Apple TV. The Remote app could take the form of a game controller, or a second screen when watching video content on the TV.

Last week at Google I/O the concept of Instant Apps was introduced. The idea is that the mobile operating system can quickly and automatically install and run a portion of an app as needed. This can be useful to interact with a parking meter, or load content within an app if someone sends you a deep link. It occurs to me that this is similar to my idea for iOS extensions to tvOS apps, except it is more generic and useful for a lot of situations.

Imagine you launch CrossyRoad on your Apple TV. Then you hold your iPhone next to the Apple TV, and iOS asks if you would like to install and launch the CrossyRoad companion game controller app. This would be much easier than trying to find the app in the iOS App Store.  Ideally the companion app wouldn't even show up on the home screen once installed unless CrossyRoad is currently running on a nearby Apple TV.

We also need a nice communication framework for iOS apps and tvOS apps to interact with each other.

I hope we'll see some innovations like this at WWDC this year. Until then, cut the cord and try my MythTV app.

Sunday, November 15, 2015

MythTV on the New Apple TV

For years I have wished there was an App Store for the Apple TV. Like most people, I looked forward to things like games or streaming video content beyond the limited offerings bundled with previous version of the Apple TV. I also wanted something else: a MythTV Frontend.

MythTV is an open source project that helps you build your own digital video recorder (DVR). MythTV has a client/server architecture, called Frontend/Backend respectively. Ideally the Backend lives in a wiring closet or server room. A Frontend is attached to each television and plays content stored on the backend.

A MythTV Backend is fairly easy to set up with PC or Mac hardware and a networked television tuner such as HDHomeRun. A MythTV Frontend is more challenging to set up. It usually involves finding hardware that supports video decoding and has proper Linux support. You also need an IR receiver and a remote. Configuring the IR commands can be challenging. I used to tell people that MythTV is more of a hobby than a solution.

That all changed with the new Apple TV.

I received my Apple TV developer kit about six weeks prior to the launch of the New Apple TV. I immediately began building a MythTV application for tvOS. The MythTV Backend has a REST API that provides a great way to access content and data. Things went pretty smoothly and the MythTV app for tvOS was in the App Store on launch day.

Thanks to the New Apple TV and the MythTV app for tvOS, it is now much easier to set up a MythTV system. For the backend you can use MythBuntu, a special build of Ubuntu that has MythTV baked in. Or you can set up a MythTV Backend on a Mac using these instructions. They may seem a bit daunting, but are mostly just commands you can cut and paste into Terminal. You'll also need a HDHomeRun. You don't need one of the new models. Mine is a dual tuner unit that is about 10 years old, pictured above. The older models can be found on eBay for around $50. For the Frontend, just use buy a new Apple TV and install the MythTV app. Now you have a TiVo-like DVR system and you can watch your recordings from any TV in your house.


The MythTV app for tvOS currently has the following features:
  • Recorded programs are listed and multiple episodes of the same show are grouped together. 
  • Top Shelf integration: quickly find and launch a show from the Apple TV home screen.
  • Scrubbing with snapshot thumbnails.
  • Fast-forward supports several speeds.
  • Watch content more quickly with 1.3x fast-forward (good for things like talk shows).
  • Easily skip commercials with 30-second jump forward and 8-second jump back.
  • Pick up where you left off. Playback progress is stored and synced across all your Apple TVs.
  • Delete shows when you are done watching them.
One feature that is not yet ready is the Program Guide. Until this is done you can use MythWeb, a web interface that runs on the MythTV Backend. It allows you to browse listing and manage schedules and recording rules. This works out pretty well because once schedules are set up (TiVo calls them "season passes"), the Backend pretty much runs on autopilot and doesn't need much maintenance.

As more content becomes available from streaming sources, "cutting the cable" becomes more attractive. One of the remaining barriers is recording and "time-shifting" local broadcasts. MythTV and the MythTV app for Apple TV fill this gap.

Apple TV apps can't be viewed in a web browser, but you can see screenshots below.







Thursday, June 11, 2015

Guard is Good (Swift)

Several good fixes and improvements to Swift were introduced at WWDC15 as a part of Swift2 -- the first major update to the excellent Swift programming language. One of these updates was the new `guard` keyword. It immediately resonated with me because I saw that it fixed some pain points that I have often encountered.

Pyramid of Doom


Anyone who has used Swift is familiar with the `if let` construct. It is an elegant way to unwrap an Optional, and do something with the unwrapped value if it is not nil. This leads to code that looks like this:

    func personFromData(data:NSData?) -> Person? {
        if let data = data {
            let json = JSON(data:data) // SwiftyJSON
            if let firstName = json["firstName"].string {
                if let lastName = json["lastName"].string {
                    return Person(firstName:firstName, lastName:lastName)
                }
            }

        }
        return nil
    }

Even in this small example, you can what has been referred to as the Pyramid of Doom.

Swift 1.2, released earlier this year, added support for unwrapping multiple Optional values at once with `if let`. This looks a bit better:

    func personFromData(data:NSData?) -> Person? {
        if let data = data {
            let json = JSON(data:data)
            if let firstName = json["firstName"].string, 
                   lastName = json["lastName"].string 
            {
                return Person(firstName:firstName, lastName:lastName)
            }
        }
        return nil
    }

Note that we couldn't completely collapse the pyramid because we have to convert the NSData to a JSON object, and you can't throw that statement in with the other assignments that are unwrapping Optionals. 

One problem with the examples so far is that there is no error handling. While it's nice to unwrap multiple Optionals at once, sometimes you might need unique error handling for each nil Optional. That means we're back to the Pyramid of Doom, except it's even worse now:
        
    func personFromData(data:NSData?) -> Result<Person, String> {
        if let data = data {
            let json = JSON(data:data)
            if let firstName = json["firstName"].string {
                if let lastName = json["lastName"].string {
                    return Result(value:Person(firstName:firstName, lastName:lastName))
                }
                else {
                    return Result(error:"missing lastName in JSON")
                }
            }
            else {
                return Result(error:"missing firstName in JSON")
            }
        }
        else {
            return Result(error:"where data was nil")
        }
    }

This is really ugly. Even in the small example above you can see that it's hard to associate the error handling code in each else clause with the corresponding `if let` that failed because of a nil Optional. The error handling code for each error condition is in the reverse order of the code that checks for the error conditions. 

Guard all the Things


Guards are kind of like `if let`, but inverted. Instead of using `if let` to unwrap an Optional while testing for nil, use `guard let ... else` to unwrap the Optional. If the Optional is nil, the else clause is executed. You have to return from the else clause. Our example can now be rewritten like this: 


    func personFromData(data:NSData?) -> Result<Person, String {
        guard let theData = data else {
            return Result(error:"data was nil")
        }
        let json = JSON(data:theData)

        guard let firstName = json["firstName"].string else {

            return Result(error:"missing firstName in JSON")
        }
        guard let lastName = json["lastName"].string else {
            return Result(error:"missing lastName in JSON")
        }
        return Result(value:Person(firstName:firstName, lastName:lastName))
    }

This is much better. Observe that the code to deal with errors is next to the error condition that was tested. Also, once all of the error checking is out of the way, the code that continues on for the no-error situation is no longer indented several levels deep. 

Guards can be used to check any condition -- they aren't just tied to Optional unwrapping. For example: 

        guard index <= 3 else {
            return Result(error:"Index out of bounds")
        }

This is not drastically different from what could be done before, however, the nuance is interesting. The alternative looks like this: 

        if index > 3 {
            return Result(error:"Index out of bounds")
        }

The version using `guard` reads better because the expression indicates the success state. It reads more like an assertion. Also, with guard the compiler requires a return in the error clause. A common programming mistake is to log something about the error but forget to return, allowing program execution to continue as though there was not an error. 

Naming Things


In the first code examples above, we used the common convention 
    if let data = data {

With `guard let,` we can no longer do this because the new constant isn't constrained within a new scope. We have to use a different name for the Optional and non-Optional versions of a variable or constant. Naming things is hard, but the benefits of using `guard` are worth it. 

Swift continues to evolve and become even more powerful and enjoyable to use. 



Thursday, January 29, 2015

(ab)Using APNS for Fun and For Profit

When we started building an event sharing social network, we didn't initially realize we were building a chat/instant messenger application. Once we added the ability to have a discussion around an event, we needed the ability to "live-update" the discussion if someone added a comment while you were in the discussion view (think iMessage). We didn't have a web socket or long-poll infrastructure in place at the time, but needed to get something working quickly.

We discovered we could use push notifications to accomplish this functionality. The challenge was to send a push notification that the app could intercept and react to if the app was in the foreground, but if the app was not in the foreground, iOS needed to ignore the push notification (no banner, sound, or badge update). This was before iOS 7 was released, so there was no official support for "silent" push notifications. We discovered we could send a push notification with an empty alert dictionary. Such a push notification didn't produce a banner if the app was not in the foreground.
{ aps: { alert: {} }, ...} 

This tactic continues to work with iOS 7 and iOS 8, and seems to get around Apple rate-limiting. The notifications are always delivered immediately. I suspect this is due to the alert in the push payload. The server doesn't think it is a silent notification, and therefore doesn't rate-limit the notifications. However, since the alert dictionary is empty, there are no visible or audible artifacts when the iOS device receives the push notifications.

Once iOS 7 was available, we used the new content-available setting to solve another problem. All of our logic to determine an accurate home screen icon badge count was in the client-side code. Because of this, the server could not send a badge value in the push notifications. iOS 7 allowed us to pass
content-available:1
which would wake up our app in the background to retrieve events from the server and calculate the badge count. We have some evidence that this does not work reliably. If the device is not charging, the push notification is received but sometimes the app does not get awakened and iOS logs an error:
“Silent Push: Deny app no resources reason: Insufficient power budget 0”

To sum up, even though it appears we can get around the rate limiting with an empty alert dictionary, iOS does not reliably wake the app to do a background fetch. 

Friday, September 12, 2014

Do we need another gadget to charge?

The Apple Watch was unveiled this week. It is certainly the result of an large amount of work from many talented individuals. The Watch looks quite polished, though still bearing some signs of a 1.0 product -- namely the shape and thickness.

One thing that wasn't mentioned is battery life. Rumors put it at "about a day," or maybe a bit less than a day. That's not very good for a watch. "Dumb" watches run months or years on a battery, and some don't require a battery change at all.

Let's stop and imagine how a watch with a battery life that short will impact your life. Think about how much time you currently spend worrying about how close your smartphone battery is to depletion, and when your next charging opportunity will be. I've seen households of teenagers where you would think their most important responsibility each day is keeping their phones charged. Now double that problem with a smart watch. Now you'll have to frequently monitor the charge level of your phone and your watch. Furthermore, each takes a different charge cable. People often charge their phone while driving. Will they now need to charge their watch as well while driving? I already have a shortage of outlets in my house as it seems that a good portion of them always have an iDevice plugged in. Airport outlets attract crowds of travelers charging their phones and tablets. These too will be even more of a scarce resource as travelers have to charge their watch as well as their phone between flights.

If we're going to complicate our lives by accumulating more gadgets to keep charged, they'll need to provide a lot of utility to make up for the increased burden.

Sunday, May 20, 2012

Solar Eclipse

There was a solar eclipse today. We weren't able to travel south to see the "ring of fire," but we did set up a telescope projection. We were able to see several sunspots before the moon eclipsed most of them.

Saturday, March 24, 2012

Pinewood Derby

Two years ago, my son William won the annual pinewood derby. Last year he placed second. This year we had to take it up a notch.
We did all the same tricks as previous years: extending the wheelbase, squaring the axles, reducing friction by polishing the axles.
This year we worked on weight distribution. We've always tried to have the center of mass as far back as possible, but this year we went to more extremes. We hollowed out most of the car. This allowed us to move more of the mass to the back of the car. We also weighted the car with tungsten this year, instead of lead.
The standard rules state that the maximum length of the car is 7 inches. For some reason, our local rules allow for a length of 7 3/8 inches. The rules that they hand out each year look like a 20th generation photocopy, so perhaps the pine blocks were longer in the past. Thus far it appears that I'm the only one who has noticed this anomaly, so our wheelbase is a bit longer than even the others who drill their own axle holes instead of using the standard axle slots. We place our axles right at the back corner of the car, so the rear wheels actually protrude beyond the back of the car. This allows us to put the center of mass even farther to the rear of the car without destabilizing the car.

This year we had open races after the official cub scout races. We built a second car for my daughters to race in the open races. This car was faster than any of the other cars except William's, in spite of the ribbon that was tied around the car. It was fun to see the look of horror on the faces of the boys as their cars lost to a car adorned with pretty cloth and ribbons.