kai_mactane: (Default)

Back when I got my Palm Prē, I noticed that it wanted to store various of my information on Google’s servers. I thought I’d kept it from doing so; I sure wasn’t using Gmail on a regular basis. I configured the Prē’s email client to check my own account on mactane.org, and I thought everything was fine.

Eventually, I gave up on the Prē and switched to my current, Android-powered Samsung Epic. I figured I was in for a boring day of transferring my contacts over manually… until I discovered that many of them had been synced to my Gmail account, and so they showed up in my new phone without me having to do anything.

Considering all the work I had to go to in order to get my to-do list items, memos and notes transferred over manually… I decided that having stuff transfer automatically was actually pretty damn cool. Since I got my Epic, I’ve been picking “Save contact to Google” whenever I create a new contact. So, if I accidentally drop my phone on the street and it gets run over by an 18-wheeler and then the fragments get kicked into the bay and sink to the bottom, I can just buy a new Android phone and have all my contacts “magically” appear there.

On the other hand, all my contacts are sitting on Google’s servers.

Read the rest of this entry »

Originally published at Coyote Tracks. You can comment here or there.

kai_mactane: (Default)

Since two of my friends have bought new Android phones in the past two weeks, I think it’d be helpful if I wrote up a quick guide and some app recommendations for those entering the Android world.

Quick Tips

Android version numbers went: 1.5, 1.6, then 2.0, 2.1, 2.2, and 2.3, and now the latest 3.0 release. Starting with 1.5, releases get code-names that start with successive letters of the alphabet, and which are based on “sweet things” or desserts. 1.5 was Cupcake, then 1.6 was Donut. The “Eclair” code-name is applied to both 2.0 and 2.1.

Most modern Android phones should (hopefully) be using at least version 2.2, “Froyo” — or 2.3, “Gingerbread” if they’re nice and up-to-date. The 3.0 “Honeycomb” release is currently intended only for tablets.

Since there’s no way to right-click on things with a touchscreen, Android uses the long-tap, or tap-and-hold, method. This is probably familiar to Mac users already. Try long-tapping on things; you’ll find a lot of features that way.

The home screen is not just one screen; it’s anywhere from 3 to 7 of them, depending on what particular model of phone you’ve got. Just swipe left and right to access the other home screens.

Read the rest of this entry »

Originally published at Coyote Tracks. You can comment here or there.

kai_mactane: (Default)

A few nights ago, my Palm Prē got dropped, causing a hairline fracture in the touch-screen. Since it would no longer take any screen input, it was suddenly an even less useful device than usual. I’d been thinking of switching to an Android phone anyway, so I am now the (proud?) owner of a shiny, new Samsung Epic 4G (one of their Galaxy S line).

Getting used to it has occupied a fair bit of my time, but here are a few early impressions. Obviously, some of these are impressions of the Android OS, and others are about the phone’s hardware.

  • The Android calendar will let me set alarms anywhere from 1-99 units in advance of events, where the units can be minutes, hours, days, or even weeks. This actually beats what the old PalmOS used to let me do (and the webOS replaced by a simple drop-down of 5, 10, 15, and 30 minutes, 1 hour, and 1 day — not very useful; sometimes I want 3 hours’ warning).
  • The Epic is a much bigger, chunkier device than the Prē was. It still fits in my pants pocket, but not so smoothly. Not only is it just plain larger than the Prē, it also has less-rounded corners. Also, the protective case I got for the Epic is the rubberized kind, noticeably thicker than the “invisible skin” I had on my Prē.
  • What’s with the battery gauge not giving an actual percent? That seems so… naff. I’ve found a nice app to give me usable information: Modded Logic’s Battery Status Bar.
  • Live Wallpaper is cool as anything. It also seems to eat batteries like a very hungry thing. I’m still trying to decide if it’s worth it or not.
  • Read the rest of this entry »

    Originally published at Coyote Tracks. You can comment here or there.

kai_mactane: (Default)

I’ve written before about augmented reality, Sixth Sense, and so on. Here’s a question: Is this really augmentation? As augmented reality takes hold, we’ll have more and more people wandering around looking at their smartphones’ screens rather than what’s actually in front of them. The smartphone delivers some extra information, of course, but it imposes a cost, too: the information takes a while to arrive; it takes attention to process; focusing on the screen means sacrificing practically all your peripheral vision…

It’s a trade-off, and I’m probably missing some aspects of it. What I’m wondering about, simply, is whether the trade is a net gain or a net loss.

Another way to put this — in harshly evolutionary terms, in fact — is: If someone with augmented reality and someone without it were competing for some life-or-death resource, who would win?

Read the rest of this entry »

Originally published at Coyote Tracks. You can comment here or there.

kai_mactane: (Default)

Right now, the question of what you need in a mobile computing platform is most often phrased in terms of “Do you need a netbook or a full laptop? Or perhaps one of the new high-end smartphones will manage?” I think the question isn’t one of capabilities as much as it is a question about how we access those capabilities.

For some people, the iPhone’s lack of a physical keyboard is a deal-breaker. For me, the smaller-than-standard keyboard on the average netbook is a powerful disincentive: If I had to use one, it would slow down my interaction with the netbook — and if I learned to be fluent and productive with the small keyboard, it might mess up my muscle memory for dealing with full-size keyboards on my “real” computers. It’s not a trade-off I’m willing to make.

The Palm Prē’s physical keyboard is tiny. I can only key it with my thumbs, and there’s no risk of interference with my pre-existing keyboarding skills. Inputting data with it is achingly slow, but offset by the device’s wonderful portability (it fits into a pocket even easier than an iPhone does). But I can’t really edit text with it, because there’s no D-pad to do precise cursor positioning with. Even the Orange+finger-movement trick is balky and awkward, in my experience; if I want to correct a single-letter typo, getting the cursor after the incorrect character so I can backspace and correct it is such an ordeal, it’s often quicker and easier for me to use Shift+Backspace to delete the entire word and then retype the whole thing.

In effect, even though the phone has the ability to edit text, the interface makes it so difficult that I can’t use the capability. It might as well not be there. What would a better interface mechanism look like?

Read the rest of this entry »

Originally published at Coyote Tracks. You can comment here or there.

Profile

kai_mactane: (Default)
kai_mactane

July 2011

S M T W T F S
     12
3456789
101112 13141516
17181920212223
24252627282930
31      

Syndicate

RSS Atom

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated Jul. 21st, 2017 06:44 am
Powered by Dreamwidth Studios