Skip to main content

Samsung Galaxy Tab 10.1 Review

As a little palate cleanser, I thought I would do a quick blog today about my new Samsung Galaxy Tab 10.1, in case any of you are thinking of buying a tablet.

The Apple Newton

Executive Summary:  I'm pretty sure you should get an iPad.  

But there are some things I learned while trying to get used to my tablet that could help you make your own decision.  If you read "the literature" online, you will see lots of people comparing screen brightness, processor speed, and number of applications available in the respective Android and Apple application stores.  Yadda yadda.  Here's what you should really think about first.
  1. Battery management:  it turns out you will want to use the device on battery power.  It's meant to be a "portable" sort of thing.  So find out before you buy:  how many hours do you need to charge your tablet compared to the number of hours it runs without being plugged in?  How long is the battery life of your device?  What applications are available to help you conserve the battery WITHOUT rooting the device and voiding the warranty?  Hint:
    1. Kindle charges fast and lasts forever.
    2. iPad charges pretty fast and lasts pretty long.
    3. SGT10.1 requires 10 hours of charging for 10 hours of useful life.  Sort of a 1:1 mapping.  Easy to remember, I suppose!
  2. File transfer:  can you connect your tablet with a cable to your PC and transfer files back and forth?  Like your music files, for example?  Hint:
    1. If you have an Apple PC, like a MacBook Pro, you will be able to transfer files to your iPad and vice-versa.
    2. If you have a PC running Windows, like a Dell, or an Acer, or a Gateway, you will be able to transfer files to your iPad or your SGT10.1.
    3. If you have a MacBook Pro you will not be able to transfer files via cable to your SGT10.1.  There are many unhandy workarounds, however.
  3. Itunes:  if you are unable to move your music files to your tablet, can you simply rev up your iTunes app?  Whoops, no, sorry, that doesn't work on SGT10.1 
  4. Headphones/microphone:  what if you want some kind of high-tech noise blocking headphones for your new tablet?  You will probably be fine if you get third party headphones, if they don't have a microphone built in, but you need to be very careful about buying third party headsets that include a microphone, because Samsung/Nokia map the connector for headphones/microphone backwards compared to the way Apple/Blackberry do.  In general, headsets marked "iPod compatible" won't work with your device and vice-versa.  Bose has a whole set of different connectors to deal with this, but most headset vendors just do it one way--the Apple way.
  5. Operating system upgrades:  if the manufacturer of your operating system issues a new update, what do you need to do to get it on your device?
    1. Kindle:  no idea, actually.
    2. iPad:  Apple has supported all devices with all upgrades it has ever done.
    3. SGT10.1:  you need to wait for Samsung to decide if it feels like upgrading your version of Android.  But that's okay, because the upgrade will break a bunch of your applications anyway.
  6. Forgotten A/C adapter cord:  what happens if you leave your power adapter at home when you go on vacation?  If you have an iPad, you can walk into any Radio Shack, Target, or Walgreens and pick up a replacement.  If you have the Galaxy Tab 10.1 you just go ahead and run out of battery because nobody stocks these, and the connector is so proprietary nobody is even allowed to think about building a third-party replacement.  Of course if you never forget things like power adapters, this doesn't matter to you.
  7. Animated wallpaper:  Does your chosen tablet allow you to equip it with animated wallpaper that looks like a bunch of swaying, decorated Christmas trees in a snowy landscape, and every once in a while Santa flies by?  I'm psyched to say that I have equipped my SGT10.1 with just such a wallpaper, and it makes me happy every single time I pick it up.  It also shows the sky with day-of-time-appropriate lighting. 
I'm not sure if iPad supports this marvelous functionality, but it's a good thing SGT10.1 does, because otherwise I might feel a little bad about what I got!

Popular posts from this blog

A Corporate Agile 10-point Checklist

I'm pretty sure my few remaining friends in the "small, collocated team agile" community are going to desert me after this, but I actually have a checklist of 10 things to think about if you're a product owner at a big company thinking of trying out some agile today.  Some of these might even apply to you if you're in a smaller place.  So at the risk of inciting an anti-checklist riot (I'm sorry, Pez!), I am putting this out there in case it is helpful to someone else.

Here's what you should think about:

1.Your staffing pattern.  A full agile project requires that you have the full team engaged for the whole duration of the project at the right ratios.  So as you provision the project, check to see whether you can arrange this staffing pattern.  If not, you will encounter risks because of missing people.  Concretely it means that:
a.You need your user experience people (if applicable) and your analysts at the beginning of the project, as always, b…

The Agile Business Case

Many agile teams have never seen a business case, ever, and they may even be proud of it.

Our mantra is that we deliver "business value," not just "software," quicker, better, and faster, but if so, we certainly don't spend a lot of time reporting on value delivery, and in fact we may be scornful about "analysis paralysis."  As software developers, we consider ourselves to be doing quite well if we can deliver the software every two weeks (or continuously).  And this is particularly if we've enabled this frequent high-quality delivery through automated testing and automated build-and-release techniques.  We've reduced business risk by making results visible more often, and allowing the business to change direction more frequently.  We assert that along the way of course we're also delivering value.  But how would we prove it?

I've recently posited that we shouldn't even think of doing agile projects without capturing and recording s…

Requirements Traceability in Agile Software Development

One of the grim proving grounds for the would-be agile business analyst (henceforth "WBABA")  is the "traceability conversation."  Eventually, you will have to have one.  You may have seen one already.  If you haven't, you may want to half-avert your eyes as you read further.  It gets a little brutal.  But if you close them all the way, you can't read.
WBABA: in summary, we complete analysis on each story card, and then we support the developers as they build it that same iteration!Corporate Standards Guy:  but how do you do traceability in agile?  You have to have traceability.  It's broadly recognized as an important factor in building rigorous software systems. These software systems permeate our society and we must entrust them with lives of everyday people on a daily basis. [The last two sentences are an actual quotation from the Center of Excellence for Software Traceability website!] WBABA: [cowed silence]Corporate Standards …