Skip to main content

The good, the bad, and the Moto X

Build quality

At first it felt cheap and plasticy compared to my Nexus 4. Now it feels right and the Nexus 4 feels heavy and the glass feels like it could shatter at any moment.

And before you ask, no I did not get to customize the colors of my Moto X, I purchased the developer edition which is only available in black and white. Which is fine, I'd rather have that than a locked colorful version.


The screen is fantastic. Watching a video on it makes the phone melt away and leave only the media.

Touchless controls

The idea behind touchless controls is pretty cool, but in practical application, touchless controls are useless to me. This is 100% because of my security paranoia though. I have PIN on every mobile device I own and I trend towards the security side of the spectrum instead of the convenience end. Having to manually enter a PIN for every voice request completely removes the less from "touchless". My two hours of using the Moto X before configuring a PIN hinted at it's potential though and for those not as concerned with security, this will be fantastic for everyday use.

Active display

One small part of this feature seems so unimportant before experiencing it, but after only a short period, I don't ever want a phone without it. Simply taking the phone out of your pocket (or flipping it over on the table) automatically displays the current time. I know what you're thinking...that it's really not that difficult to hit the power button to turn the screen on and off. And you're right, it's not that hard. But this just feels so much better!

The main feature of showing notifications without having to turn the phone on useful too. It even works with a security PIN and will lead to fewer unlocks as you can check out the snippet and decide if any actions need to be taken.

Motorola device policy

With the device manager you can remotely lock, locate, or wipe your device. It's kind of odd that Motorola is offering this as Android now has it built it. I opted not to use it as I've already got the built in device manager, and Google Apps device manager setup.


The camera interface minimalist and stays out of your way so you can get the job done.

I didn't think much of the quick capture camera at first. It seemed like a gimmick for the sake of being flashy, and in some respects it is. But it's also an elegant solution needed because of how the active display changes the interaction model. In existing phones you always have to hit the power button to turn the screen on. At that point it's a simple swipe on the lockscreen to bring up the camera and start snapping away. But with the active display, you get of the habit of seeing the lock screen unless you have the intent to unlocking your phone. The double wrist twist is simple, fast, and easy.

Touch anywhere to take a photo is nice. I do miss the standard Android interaction of tapping to focus and I've already had one macro shot I was taking that was focusing on the wrong distance. A small price to pay I guess.

Burst mode is dangerous, it's so easy just to hold it and hold it and hold it. I'm sure that will come back to haunt my battery one of these days. Pro tip: use it with Google+ photos to get some #autoawesomes!

Sadly photospheres are not currently supported. Hopefully support will be added in a future software update.


Popular posts from this blog

CloudSense: the Future of Advertising

With the whole cloud taking off and more and more services switching to a push it into the cloud, leave it there until you need it, and pull it out model. I can only imagine what will be switching to this model soon. Oh wait. I can imagine.


Reading an article about how Avril Lavigne is supposed to have a $2 million check "appear" in her mailbox because of the absurd number of streams her videos get from YouTube got me thinking about creator compensation. The problem Avril is having is, a) Google wants to keep the money, and b) Google is having trouble figuring out how to monetize video streams. But on a grander scale it is whoever puts the ads on the page that gets the money not the content creator.

Little known @Twitter and @TwitterAPI tips and tricks

Be sure to comeback as new tips and tricks get added. If you know of anything I missed be sure to let me know.

Static URL for profile images based on screen_name:

* This performs a http redirect to the actual profile image URL. Currently https redirects to http. You can also add "?size={mini | bigger | normal}" to get specific sizes.

Redirect to profile based on user_id:

In_reply_to_status_id mentions:

* In the web interface new mentions are only replies if they start with @screen_name. By pushing @screen_name further along in the string your followers who do not follow @screen_name will still see the status.

Profile image sizes:

* By default you get the original image size you can add _mini, _normal, and …

Installing Storytlr the lifestreaming platform

"Storytlr is an open source lifestreaming and micro blogging platform. You can use it for a single user or it can act as a host for many people all from the same installation."

I've been looking for something like Storytlr for a few months now or at least trying to do it with Drupal. While I love Drupal and FeedAPI I did not want to spend all that time building a lifestream website. So I've been playing around with Storytlr instead and found it very easy. Here is how I got it up and running on a Ubuntu EC2 server. You can also check out the official Storytlr install instructions.

LAMP stack installed and running.Domain setup for a directory.MySQL database and user ready to go.Lets get started!
Get the code: wget tar -xvzf storytlr-0.9.2.tgzYou can find out the latest stable release on Storytlr's downloads page.

Import the database:
Within protected/install is database.sql. Import this into your empt…