It was a very interesting talk – which I may get into in more detail in another blog post – but my interest was piqued on another topic before our guest speaker even took the stage. While waiting for everyone to take their seats I was socializing with a few of the other attendees. In advance, if either of the two ladies I was speaking to tonight end up reading this – I’m very sorry I forgot your names!

During some light conversation about our interests in user experience related fields – one of these ladies (we’ll call her Alice) wanted to add the other (we’ll call her Brenda) to LinkedIn. Alice asked Brenda if she was on LinkedIn, and after Brenda said yes, Alice proceeded to pull out her BlackBerry to look Brenda up.

It was at this point that I asked them “won’t it be interesting when your phone will have opened up LinkedIn and already searched for Brenda because it heard our conversation?”. We all kind of laughed, and commented on how that technology was not quite ready for that yet with big smiles. Phones reacting to your conversations? Sorcery I say!

However ridiculous this concept sounds, we might not be that far off.

Technologies such as Microsoft’s Xbox 360 Kinect have (as I’ve heard) very intelligent voice detection – to the point where it knows the difference between the voices of the users in the room. It’s not a stretch to imagine Microsoft putting similar technology into their newly launched Windows Phone 7 to enable this very sort of thing. It would be a very interesting shift in user experience design for applications to know what you want to do before you’ve decided to do it.

This is a guest post by Dana Harrison. Check up on his other activities at The Linux Experiment and his other posts on audiophonik.

Hi, all!  You may have noticed already by reading my slightly different name, or perhaps you’ve heard of me over on the wildly popular site I co-founded, The Linux Experiment, but I am not the usual Phil.  My name is Dana, and I’m a young professional working in Information Systems for a large insurance company.  I work with Phil and also had the pleasure of founding The Linux Experiment with him.  This is my third guest post for audiophonik.

This time around, Phil has asked me to do another review for an application available on Google’s Android platform: the shiny and efficient ChompSMS, now running on (yay!) Android 2.1 as my carrier – Rogers – has finally pushed out this update to my HTC Magic+ hardware.

ChompSMS: Sounds tasty

ChompSMS is an Android-only (and decidedly rather handy) replacement to the built-in ‘Messages’ application used for sending and receiving MMS / SMS / pretty much any other kind of MS / on the Android platform.  To give you an idea of how stone-age their own messaging application is, I can’t notice any change between its current iteration – on Android 2.1 – and the one that was on my phone last week, using Android 1.5.  I’m almost tempted to root my phone and slap on Froyo, just to see if there’s any difference in the stock messaging app.

Old and busted...

...new hotness.

ChompSMS is supposed to offer a lot of new features and generally ‘beef up’ the stock messaging options available on Google Android, and comes with a huge list of things it supposedly does better than Google.  Among them:

• The UI has been changed to mirror that of the iOS platform – which I could really do without, but it looks better than stock
• The ability to send SMS / MMS over the ‘ChompSMS’ network with the purchase of ‘credits’, for a much cheaper rate than your provider
• A host of new notification options for you to choose how you’re notified about received (or even sent!) messages

Now, that’s certainly a lot to claim: let’s see how ChompSMS stacks up against its supposed abilities.

Finger-Chompin’ good

Now, I can honestly say that I haven’t personally purchased credits or paid for ChompSMS in any way.  While it does tout itself as a ‘free program’, there is a premium version available for a few bucks that will remove the streaming advertisements from the program’s main window.  In all honesty, they’re pretty out of the way, but I have accidentally tapped on one or two while attempting to select the top name on my messaging list, mostly due to my own poor motor skills.  If ads are the sort of thing that really piss you off though, go for the paid version; I’m seriously considering it.

The first three things with which I immediately fell in love using ChompSMS are as follows:

1) Notification options

Seriously, this should just be available in the stock version of the Android messaging application, but apparently Google has not yet looked that far into the future and gleaned that much information from its search engine users.  ChompSMS grants me the ability to use either my LED (located near the earpiece) OR the trackball (which pulses white) – or BOTH! – to notify me of texts.  On top of that, I can even select what colour I want the LED to flash, and it’s much easier to select any of my usual songs as a notification sound – no silly messing about with folders on the SD card.

2) Truncated message strings

On top of the fact that it just handles message strings more beautifully – much more intuitively than the stock application – one issue I ran into several times with the stock application is the fact that, well, some of my message strings get rather unwieldy, and I don’t want to have to delete texts to use my application.  For example: before erasing my phone for the big Android 2.1 update, I had over 3000 some messages with my girlfriend that I didn’t particularly want to get rid of.  Trouble is, every time I opened her string in the messaging application, it would take forever to load all of those messages.

This is where ChompSMS comes in handy: it only loads the last ‘so many’ (I say this because I haven’t counted) messages immediately, with the option to ‘open older messages’ at the top of the string in button form.  As it turns out, this has been a total lifesaver in that I’m now not waiting forever for my messages to come up, and the application itself actually has a smaller footprint as it’s not loading every single text in the history of mankind into memory.

3) Replies from the lock screen

This is honestly a no-brainer.  The quick ability to reply as soon as a message comes in – even right from the lock screen – is just about the handiest and simplest thing they could have thought of.

The ugly

The only things I’ll complain about with ChompSMS are as follows:

1) It shouldn’t have to mirror the Apple iOS UI for texts in order to remain functional and pretty.  They should really try to ramp up development of their own, better-than-Google-and-Apple UI to distinguish themselves from the rest of the garbage out there.

2) I hate ads. Honestly, you would think they make enough from people purchasing their damn ‘credits’ to send texts over their network to be able to remove ads from the free version of their program; I’m totally torn about whether or not I want to shell out a few bucks for a messaging application, or just remove it and use the stock one again.  Or just toss a few Google ads on your site – nobody would even mind!

The closing statement

All in all, ChompSMS is almost a necessity for someone who texts as much as me – I almost regularly come close to my 1000-text-per-month cap on my plan with Rogers, but am usually careful not to get too close to the top because I know how much they love to bleed me for money.  If you’re a more recreational, or less frequent, texter then I would imagine you can stick with the stock application and be just fine, as long as you’ve paired it with something like Swype.

Go to your Market, get ChompSMS, and be happy – you will thank me later.  Here’s a handy QR code for Android users!

This is a guest post by Dana Harrison. Check up on his other activities at The Linux Experiment and his other posts on audiophonik.

Hi, all!  You may have noticed all ready by reading my slightly different name, or perhaps you’ve heard of me over on the wildly popular site I co-founded, The Linux Experiment, but I am not the usual Phil.  My name is Dana, and I’m a young professional working in IT for a large insurance company.  I work with Phil and also had the pleasure of founding The Linux Experiment with him.

For reasons unbeknown to me, Phil asked me a few months ago to install Slide Screen for Android onto my Rogers HTC Dream – that’s a ‘T-Mobile G1′ for any American readers out there.  Slide Screen is basically a complete home screen replacement for the standard Android interface, and is meant to reduce screen clutter and information overload in a nicely presented, simple, single location.

Installation and Setup

This was just about the simplest thing in the world, as is the installation of most standard Android applications.  Open up the Android Market, search for Slide Screen, and install.

Setup was also quite simple, offering the option of either completely replacing my home screen (which I chose) or running as a launchable application.

First Impressions

I have to hand it to the folks at Larva Labs – they know how to code a nice-looking interface.  The Slide Screen interface is certainly clean if nothing else, but while preventing me from experiencing information overload, I feel I may have been left out of information altogether.

Among other frustrations, I found the Slide Screen application significantly slowed down the all ready slow ROM included on the Rogers HTC Dream.  In addition, the constantly running application reduced battery life noticeably.

The notification widget for missed calls also, inexplicably, did not actually bring me to my call log(s) as expected, but instead populated the number in my phone application for quick dialing.

I also found the ‘simplification’ of information rather strange.  Instead of keeping the information I want in plain view, I found that the application held information I want in inconvenient (ie, having to launch it myself) places.

Final Thoughs

While I can see the merit in this application, it’s not specifically for me.  If the folks at Larva Labs can find a way to integrate more popular applications into the main screen while reducing overall memory footprint, I may explore it again in the future.

For now, I am falling in love with the Sense interface of my HTC Magic!

It seems though, that while I was off dreaming of the future, Ford decided that the future is now. At this year’s CES, Ford showed off its expansions on sync, as well as their new MyFord prototype. The MyFord prototype featured a single, giant, Volkswagen-esque speedometer, with a digital display on either side. As Engadget points out in their coverage of MyFord at CES, the kicker of the whole MyFord setup is the 8-inch touchscreen display in place of traditional radio controls. This is where SYNC will display information, and allows for a slew of features – including 3G/4G connectivity, and an in-car browser.

Ford didn’t just limit their news to hardware, as they announced what they’re calling the “Sync App Ecosystem”, which will allow smartphone apps to easily hook into a SYNC API. They also announced increased support for different mobile phones, including Android, iPhone, Palm, and Blackberry. This approach is useful because it won’t introduce yet another “app store” for you to have to buy apps from. Ideally, the developers of your existing apps on your Smartphone will just push out updates that include SYNC support, and voila! SYNC integration for everyone.

Alas, these announcements were not without some drawbacks. While the browser was by far my favourite announcement, as it would allow Hype Machine use on the go like I mentioned earlier, Ford’s has decided for safety concerns, the browser will be disabled while the car is moving. A good idea if you want to prevent drivers from reading the news or watching Youtube while they’re driving – however what about the passenger? Why can’t they use the browser? Ideally, they should be able to, without distracting the driver. Additionally, this means no Hype Machine support either – as there is still no mobile phone application for the site – even though they teased one for the iPhone back in October 2008. Even then, who knows if Flash support would be enabled.

On the hardware side of things, in what I assume is an effort to make operating the rest of the vehicle seem like operating the 8-inch touchscreen, they’ve removed traditional buttons and replaced them with touch sensitive areas. While this seems good, I can garuntee that lack of tactile feedback will not be appreciated – if for nothing else than that you won’t be able to fumble around with the controls until you feel the button you’re looking for. In fact, you’ll probably end up writing a tweet, listing yourself as “its complicated” on Facebook, and changing the radio station 8 times before you finally feel your way to the button you’re looking for. This sort of defeats the purpose of trying to create a user interface that doesn’t require the driver to take their attention off the road.

Overall I find this a much more promising development in the area of having computers in cars than the initial launch of SYNC. The new hardware opens up a lot of opportunities for developers to get in there through mobile phone apps and have a presence in vehicle. Hopefully the whole situation with browser-lock can be alleviated somehow, and the tactile feedback won’t be as much of an issue as I’m expecting it to be. Additional technical features, pictures, videos, and Engadget’s thoughts can be read in the source links.

Source: Engadget – MyFord dash and Sync App Ecosystem hands-on