Teton Hiking

The day started with some drizzle and a rainbow.

September 11, 2011 – We woke up relatively early and realized there was a bike race in Jackson.  The clues were the sold out hotel where the majority of cars had road bikes and crew signs, as well as the completely packed breakfast places.  So our breakfast spot of Bubba’s BBQ was going to be a tad crowded.  Instead we drove into town and parked down a side street and got a picnic breakfast to go from The Bunnery.  We enjoyed coffee, a ham and cheese croissant and an almond pastry twist (all excellent – this is our new breakfast spot in Jackson!) while overlooking the Teton Mountain range.  The pastries were fresh and perfectly flaky, and the coffee was hot and adequately strong.

Thankfully we did have some clear weather for hiking.

After breakfast we drove on over to the Bradley and Taggert Lakes trailhead.  We had a great hike, sunny and breezy – like a perfect Fall day, even the aspens were beginning to turn color and the air made us (or at least Louisa) think of apple cider (and apple cider donuts), sweatshirts and steaming mugs of coffee.  The lakes themselves were smooth and clear… the pictures don’t really do them justice.

We prefer the view from Bradley Lake over Taggart.

The lunch spot was (naturally) Dornans – we feasted on root beer, bbq chips, and made-to-order sandwiches (think: avocado, smoked gouda, sprouts, tomato, etc., all on a chewy baguette).  We got the food to go and found a shaded picnic table by the visitor center where we could watch the storms brewing behind the mountains.  Fortunately the weather cooperated and we were able to finish our picnic lunch before it got too windy!

Storms can pop up at any time, mainly to drop hail and lightning on you. :)

Eventually it was time to stop watching the clouds swirling behind the mountains, so we decided on the Leigh Lake trailhead.  We were watching the weather and decided we had time for a quick hike before it got too interesting, and hiked about a mile down the trail and then back to the car.  Along the trail was a sweet little deer with very big ears, as well as some nice views of the water.

We're convinced that good views can be found at any lake in the Tetons.

In an unsurprising twist, we got a picnic dinner to go from Dornans.  Dinner was very similar to lunch except with NY cheddar kettle chips (we preferred the BBQ flavor from lunch), both root beer and huckleberry cream soda, and a rice krispies treat for dessert.

And because we can, here is another lake view photo.

Dinner was enjoyed along the fairly short and uneventful drive (about 5.5 hours) to Salt Lake City, which brought us back to the Hampton Inn.  Tomorrow we fly back to Charleston, after a wonderful (and wonderfully tiring) vacation!  We’re transferring through Chicago (Midway) again, and anticipate some Potbelly sandwiches are in our future. ;-)   And since this is a September 11 post, it seems like it calls for some words about the events of 10 years ago… but sometimes words are inadequate.  It was a dark day punctuated by selfless bravery.  May we remember and honor those innocent people who died in NY, PA and DC, of whatever nationality, background or faith, without becoming consumed by bitterness and hatred.

The Bunnery Bakery & Restaurant on Urbanspoon

Google+ Initial Impressions

After finally receiving a Google+ invite today, I decided to take the service for a spin to see what sets it apart from other social service like Facebook and Twitter.  Here is a quick list of thoughts that I have so far:

  • Circles – Finally, a way to share posts with a subset of users.  If I have posts that are only relevant to a specific group of users, I can simply specify that circle when posting content. This is great for posting info for a specific geographic location (local concerts, expos, LAN parties…), or specific interests (technology, birds, photography, LAN parties…).  This is a killer feature for me, and will likely decrease my use of Facebook and Twitter.
  • Hangouts – Free group video chat with some cool other features.  The coolest use that I’ve seen of this feature was when someone worked on some javascript coding while answering questions live on Google+.  Since you can have up to 10 people in a hangout at once, this should easily accommodate family chats or small-business meetings.
  • Huddle – This is a feature that lets you chat with specific people or circles while on the go. The example that Google uses is trying to organize a movie run with a bunch of people.
That’s it for now, but you can find more information about Google+ at Google’s site.

Editorial: Why aren’t Android Developers using Google’s Backup Service?

Problem

You have an Android device, and you either have a complete device crash or decide to move to a new phone.  You need a quick way to restore settings for your many applications.  What do you do?

Solution?

While you could use applications like Titanium Backup or Sprite Backup to restore your data, Google has already provided a backup service for Android phones that will automatically save application settings to their servers.  This data will be restored upon re-install of the application.  So everything is great; your Angry Birds progress is automatically being backed up for future restoration if necessary.  Right?

The Real Problem

Wrong. While the solution above sounds great in theory, the reality is that most developers are not using this service.  I’m not the only one that’s noticed this, so why are developers not taking advantage of free backups? A few ideas:

  • Device support – The article from Google mentions that phones do not need to support this service, and that Android 2.2+ must be present.  Google also does not provide a list of devices that support the service. I’ve noticed that CM7 supports the automatic download of Market Apps previously installed on the device, while HTC Sense-based ROMS do not support this feature.  Is this a CM7-specific modification, or the Google Backup service at work? And since HTC does not do the same thing, does that mean that their devices are not using the service?
  • Ease of implementation – Google has a good Developers Guide article on getting things up and running, so ease of implementation shouldn’t be an issue.  The dev guide article is pretty comprehensive, and has better documentation than some of the other Android APIs that I have worked with.
  • Bad performance – When Google’s Backup Service was first released, dual-core phones were no where to be found and 3G was still the norm.  If this service used a lot of CPU time or bandwidth, performance would definitely be a factor. Any concerns should be lessened with most new handsets sporting a fast Snapdragon or Tegra II processor.  4G also provides faster transfer speeds for a bandwidth-intensive service. Evolving technologies mitigate performance issues that may have been present on last-generation devices.
  • Security – Security is still a concern, since the service provides no guarantees on data protection. In fact, Google states that this service should not be used to store username or password information. By extension, any private or sensitive information should not be stored by the service.  Security risks definitely limit the usefulness of the service for some developers.
  • Control – Google does not provide developers direct control over when the backup process runs.  The app can tell the backup service that the data is ready for backup, but backup doesn’t not necessarily occur immediately.  This lack of control could cause backups that run too frequently (more data usage) or backups that don’t run frequently enough (new data not backed up).

With all these potential issues, how should developers proceed?

The Real Solution

To provide the best user experience possible, I believe that an automatic backup/restore solution is the way to go.  I have two implementation ideas for developers to make this happen:

  1. Actually use Google’s Backup Service. This solution would be best for single-player games that store game progress. (Angry Birds, I’m looking in your direction.)  There’s nothing more frustrating than switching phones only to find out that all game progress was lost after re-installing the app.  General preference information in any app would also be a good candidate for this approach.  This solution would not work for services that store sensitive information due to the security restrictions listed above.
  2. Use your own cloud-based service to store information. Apps like Foursquare already do this, only using on-device storage to cache information temporarily. This approach would work well for any application that has a cross-platform presence, or needs to control the frequency of data backups. It would also be more customizable than Google’s service, providing flexibility to encrypt data for transport and storage if necessary.  Look to services like Facebook, Twitter, and Foursquare to see how a custom cloud service operates.

If you have an opinion, suggestion, or comment to share, please post below.  Better yet, send them to your favorite Android developer to help spread the word on automatic backups and restores!

Sprint Evo 3D: Review Roundup

If you’ve been trolling the web during the last day, you’ve probably seen reviews for the Evo 3D popping up like mad.  I’ve listed my favorites below, along with my commentary and opinions as an Evo 4G user.  The biggest question that I have after reading through these reviews is the device’s battery life.  A lot of these reviews mention terrible battery life, but they don’t specify if they are always running with 4G enabled. I’ve found that the Evo 4G eats battery with the 4G radio on, but I’ve had great battery life with Wi-Fi or 3G when in a good coverage area (~2 days of normal use, especially on Wi-Fi).

Takeaways:

  • The phone hardware is great, and Sense 3.0 seems to be a nice upgrade.
  • WiMAX is a poor competitor to Verizon LTE, and can drain battery quickly. In particular, building penetration is a concern with WiMAX running in the 2.5 Ghz frequency range.
  • Glasses-less 3D screen effect is good, but not quite as good as the Nintendo 3DS. Also, expect headaches if using the effect too long (say, greater than 10 minutes of use).
  • 3D camera not useful at short distances, so don’t expect great macro usage.
  • If you are used to the size of the Evo 4G (it is BIG),  you will have no problems with this device. I like the form-factor more than smaller devices, so this is a plus for me.

Review Links:

  • Engadget – This seems to be the most comprehensive review out so far, and they hit many of the highlights and lowlights of the device.
  • This is my next… – A shorter, more to the point, review that does a pretty good job in giving an overview of the device. If you have been following the Evo 3D since its announcement, this is the best review for you.
  • All Things D – They do mention that they kept the 4G radio on and still got through most of the work day.  That is an improvement from the Evo 4G, where the battery tanked when a weak 4G signal was present.
  • Android Central – These guys love the new Sense 3.0 found on the Evo 3D.  This is an initial review only, so it is a bit short.