Ramblings in Utopia

First impressions of Google's Project Glass

Fri, 06 Apr 2012 08:58:09 -0700

Just a few comments about Project Glass after watching the concept video and seeing a few photos

So, you've probably all seen the video by now, but just in case you haven't, watch it below.

Clearly this is a concept video, just as any other you've seen in the past (the ones I always think about are the Nokia Morph and 888 ones), but this one has been released via the 'front door' rather than being leaked or simply shown as a 'concept of the future', and they've even displayed a prototype in photos and now to some tech journalists.

This photo is not just a great photo because of it being worn by Sergey Brin, it's great because you can clearly seen the complete side of the prototype device, while the official photos only show it on a long-haired woman. The reason why I think this is important is that it clearly shows that the device stops before the ear, and does not incorporate any 'Oakleys THUMP' style earbuds. Of course it's possible, and reasonable that there could be a socket for an earbud at the rear of the device, but personally I hope not, as there are plenty of bluetooth headsets that could be paired with the glasses/accompanying Android phone. The lack of earbuds does pose a question though, how the call at the end of the video works.

I wasn't planning on this initial post being a long post, so instead of going into a detailed description here are a couple of simple points of observation about that photo:

The device appears to be self-contained. The glasses frame could be concealing a wire to a secondary module, but I'm lead to believe there isn't one, and the rucksack Sergey's wearing is said to be unnecessary for the device to function.
There are no earbuds, meaning the concept video showing a call at the end can't be easily achieved unless an additional headset is worn (not necessarily a problem)
If this is self-contained, the the frame is simply a way for non-glasses wearing people to use it, and it could probably then be clipped on to existing prescription glasses. This is presuming the display does not have any need to project an image into the eye, and is just a display that floats.
The display looks like a prism, and has no back. This could mean that it's using refraction to project the picture towards the eye rather than having it float.
The side seems a little chunky for the location it is, and may obstruct peripheral vision. I would personally prefer a thinner side leading up to the corner section, and have a slightly chunkier back section near/behind the ear if necessary.

There are also a couple of questions I'd like to find answers to:

Does this require a phone/host device to function fully? I hope so, as having to have another SIM (and data subscription) would be annoying.
How is it picking up the speech commands? Having it always listening for keywords must be battery-intensive, but having a button to push could be tedious.
How does the device produce a 'full-frame' image? Since the display seems to only cover the top half of the eye, it would seem logical that the user would have to look upwards to get see the display.

I plan to do a more thorough review/comment post/video about the concept, as well as a roundup of the mobile accessories I already own and how they (or devices like them) could work together to form a holistic Personal Area Network (PAN). I'll hopefully get around to doing that this weekend, but suffice to say I think it's an awesome idea, and hope it's not too far away from production/beta testing (although I have no hope of getting to try it until it's in production).

What my tourettes was like as a kid

Sat, 14 Jan 2012 11:51:28 -0800

I just stumbled upon this video which reminds me a lot of myself when I was between 8-12 years old, and I thought I'd share it in case people were wondering how tourettes effected me as a kid.

I used to have the head movement, the arm and the squeak, among other tics. The video here shows more-or-less how I remember an average day being.

It's constant head movements like that which caused me to 'give up' reading, and be very slow at writing. I *can* read, and reading magazines, webpages, etc. isn't a problem, but reading a page of a book from start to finish can be a real chore, and it something I don't do for fun. How did I get through school/university? I learnt to do homework from when I was at junior school, where no-one else would have it, which I guess also prepared me for secondary school where the real homework starts getting dished out. In secondary school we would always roleplay any English Literature books ('Romeo & Juliet', 'Macbeth' and 'Of Mice And Men'), and following along in the book was easier then, and I picked up the skill of skimming, so in tests I could find the right part of a section of text/book without needing to read/reread a chapter or page. At university I was lucky enough to be able to pick everything I didn't already know up without the need for heavy reference books.

Nowadays my tourettes syndrome is pretty much unnoticeable (never having had any form of medication, in case you're wondering), but occasionally I have a bad day where at least I notice I'm doing something.

Unlike some though, I wouldn't want a cure for my tourettes, it's just who I am, and I attribute some great decisions in my life to having had it, one of which being my parents sending me to learn to touchtype when I was 8 pretty much as soon as I was diagnosed, which started me on my path to programming.

Ok, now for the video:

So-called standards

Thu, 01 Sep 2011 18:19:50 -0700

An analyst reader contacted me asking for some information regarding home automation standards, and since I felt like having a bit of a rant, I thought I'd write my answer as a blog post.

This has again turned into a mammoth post, so reader discretion is advised, feel free to skip over any parts which bore you... heck, I'm don't even proof-read these posts because they're TLDR :o)

First, an analogy. This evening we watched a documentary made by the BBC called 'The Box That Changed Britain', and a very notable quote from it:

"It's kind of amazing to me to look at all these boxes here, and these were all designed by Keith Tantlinger, back in 1956, and they had patents for all these, and he convinced Malcolm McLean to give the patents to the industry. So that meant everybody could come in with the same twist-lock safe-guard, and it was an amazing system."

"By giving up his patents, McLean made it easier for rivals to copy his design, rather than come up with their own ones. This encouraged standardisation, meaning that today any container can be handled at any of the world's major ports, without any problems of compatibility"

Today, the reason why things are made worldwide, and why we can afford to have those things in our lives is because Malcolm McLean and Keith Tantlinger released their patents for a greater cause. The same needs to happen for Home Automation. Until we have a standard that isn't patent encumbered, and is cheap to replicate and produce, we will not have a 'standard'.

In my previous post I do mention them as 'standards', but the whole nature of a standard is that people adopt it as the specification to use when doing X, and none of the current 'standards' (hence the 's' in standards) have managed it.

We've seen the same thing happen in video and audio media in the past, and although the best standard on paper might not win every time (and hardly ever does), we desperately need this to happen in the home automation industry. The other industries which have fought over this have been in fierce markets, and the winner has been announced in a matter of a couple of years (unless they can live 'happily' in parallel, as with many audio formats), but the home automation industry doesn't have this luxury of a fast-paced cut-throat market, they're a niche, and until they recognise that they need to work together to get into the mainstream, I'm afraid the only home automation people are likely to buy are the cheap 'Standby Saver' type of products.

Where are the home automation standards going?

Every year at CES there seems to be a whole new set of hype around more home automation manufacturers, with even more pretty touchscreen control systems but they never seem to actually get anything to the market.

For now, I personally think it's a fight all of the manufacturers are losing, and if you read the 'homebrew' section later on there might be better alternatives coming from the open source community.

So which standard would I bet on?

The 'official' approach

Well, if you read my previous post you might think I'm routing for Z-Wave, but that wouldn't be the case. I chose Z-Wave because of it's ability to be a retrofit solution, since it's completely wireless, but from comments I understand that C-Bus and Rako both are able to be retrofit, and of course a hybrid hardwire/wireless solution would be ideal, to be able to 'go anywhere'.

Apart from the pricing, I would lean towards C-Bus, from the 'standards' I've looked into so far. They have nice-looking devices, and seem to have a good technical solution

Zigbee, used in Alert-Me's products, many energy monitors, and a lot of industrial use-cases, I would like to see more of it, but for the moment it's too proprietary for me to think about.

What I'm ultimately looking for is to be able to buy a light switch for <£10 and for the average homeowner to figure out how to fit and wire the faceplates and sockets without resorting to an electrician's help. None of the standards seem to be at that stage yet, especially on the pricing.

The homebrew approach

Since I'm a geek, and an occasional hacker, I like the idea of using standard networking for the communication channel.

xPL

The xPL Project is an interesting, but somewhat neglected (marketing-wise at least) project, which is creating a standard way to communicate about home automation controls, and building software for servers and nodes in order to connect devices. I haven't been able to look into it too much because I couldn't get it build easily, and the documentation was quite frankly rubbish, but that was a couple of years ago, so that might have changed, although looking at the latest post being from 2009 I doubt too much has changed, but the code repository is still very active.

The slight problem I see with this approach is that it hopes to connect *all* dispersed standards, so they don't have enough focus on getting people up and running with one particular set of hardware, which ultimately means a lot of customisation hassle, but I could be wrong.

Arduino

On the hardware side, Arduino, an Open Source Hardware platform is here to the rescue. Being cheap and easy to build (My girlfriend and I have even soldered one together ourselves, of the Nanode variety), and coming in an amazing array of sizes and feature-sets for different purposes, from clothing-friendly versions, to ones with built-in networking, to others with radio transmitters.

I urge anyone with the slightest interest in making their own embedded electronics, to buy an Arduino and start sketching, you'll be amazed at what you could do.

This is also the platform Google chose as the avenue for the Android Open Accessory Development Kit (ADK), so there's a rather large community building up, if there wasn't already.

MQTT

I know very little about MQTT, but basically it's a very lightweight protocol for machine-to-machine (M2M) communication, which includes queueing and retransmissions as standard. It's being used in Arduino projects, most notably the Nanode community, using it for energy monitoring, and over low-bandwidth radio frequencies for remote monitoring of weather, gardens, etc.

Data Stream Communities

Pachube, among others, are getting more popular, and the power of these services to do real-time analysis, complex event processing (CEP) and triggering remote events is really going to push the boundary of what home automation, energy, and environmental monitoring can enable.

Increasingly, it seams, these services are going to be provided by communications companies, possibly in partnership with energy providers, but ultimately the communication is going to be the deciding factor for a lot of these platforms... whether we can get telemetry data from vehicles cheaply and pervasively is in their power.

Conclusion

In short, I think the 'old boys' are risking being bypassed completely by entrepreneurial 'amateurs' if they don't start to reduce prices, geographic coverage, and increase the amount of devices/controls that are available in all markets outside the US.

Arduino and other low-cost Open Source Hardware solutions are going to start playing a strong role in turning the tides on the home automation scene with a community spirited approach.

Patents are the worst thing to happen to innovation, and luckily most of the latest projects to start know that being open will get them further than staying isolated and closed, but the old-fashioned corporations don't 'get it', as usual.

For installation and home design companies the current standards going to serve fine, with people/business that are able to afford the 'job lot' being catered for, but for the average home owner who just wants to turn a few lights on and off, spending a fortune on a couple of light switches is turning them to cheaper, crappier solutions.

Arduino Binary Die

Sat, 20 Aug 2011 13:37:04 -0700

After buying a Nanode (an Arduino-compatible board with ethernet built-in) last weekend, we've been trying to work it out by making a couple of simple examples, the 'Binary Dice' is the first one with input and outputs.

A note, this code example is based on the one from the book Arduino: A Quick-Start Guide by Maik Schmidt.

You'll need (other than the Nanode/Arduino board):

3 LEDs (ours were rated for 0.8mA-0.12mA at 6V)
3 Resistors to bring the 5V down to a reason current for the LEDs (we used 680Ω)
1 large resistor to flatten out the fluctuations in the ground rail (we used 17KΩ)
A push-to-make button

Schematic and Breadboard

Made with Fritzing, just to get used to how it works.

Arduino Sketch

You may need to change the constants at the beginning to match your board and where you plug things in.

const unsigned int LED_BIT0 = 4;
const unsigned int LED_BIT1 = 2;
const unsigned int LED_BIT2 = 3;
const unsigned int BUTTON_PIN = 5;
const unsigned int BAUD_RATE = 19200;

void setup() {
  pinMode(LED_BIT0, OUTPUT);
  pinMode(LED_BIT1, OUTPUT);
  pinMode(LED_BIT2, OUTPUT);
  pinMode(BUTTON_PIN, INPUT);
  Serial.begin(BAUD_RATE);
}

void loop() {
  const int CURRENT_BUTTON_STATE = digitalRead(BUTTON_PIN);
  
  int command = Serial.read();
  
  if (CURRENT_BUTTON_STATE == HIGH || command == '1') {
    reset_LEDs();
    delay(1000);
    randomSeed(analogRead(A0));
    long result = random(1, 7);
    output_result(result);
  }
  
}

void reset_LEDs() {
  digitalWrite(LED_BIT0, LOW);
  digitalWrite(LED_BIT1, LOW);
  digitalWrite(LED_BIT2, LOW);
}

void output_result(const long result) {
  digitalWrite(LED_BIT0, result & B001);
  digitalWrite(LED_BIT1, result & B010);
  digitalWrite(LED_BIT2, result & B100);
  Serial.print(result);
}

Google+ Idea: Control your Circles with Orbits

Thu, 30 Jun 2011 17:13:32 -0700

I had an idea for Google+, inspired by Robert Scoble, so I thought I'd illustrate it properly.

I've been playing around with Google+ today, and after starting to follow some well-known people started to get bombarded with posts onto my main stream that weren't too interesting, and since Google+ orders posts in the same way as Buzz, popular posts keep popping to the top.

A couple of hours ago I commented on a post by Robert Scoble, where he called himself the 'Scoble Virus' and commented that people should put him in a circle called "noisy buttheads"

My comment was that perhaps there would be a way to easily give preferences to circles about how visible they should be on your main streams (posts, photos, etc.)

It'd be nice to be able to 'mute' specific circles from our main stream... A bit like putting people in a Twitter list without following them... we could still select the circle and see it's stream, but wouldn't get bombarded with stuff amongst our 'closer' friends and family... perhaps a way to 'distance' ourselves from certain circles, have an 'inner orbit' for our closest friends, and outer orbit(s) for others?

I had an image in my mind as soon as I wrote that comment, so I decided I'd sketch it up to see what people think of it.

The idea

The idea would be to create orbits of visibility preferences (what messages you see in your main streams and notifications). The theory would be that the further people get the less visible you would make them, so you'd put noisy people like Robert Scoble into a far away orbit and only 'visit' occasionally.

The circle would still be listed alongside the main streams, but the circle icon would show as greyed out on stream pages where they won't show up.

Sure, you could put these toggles directly on the circles page, but I think the page would get a bit too complex. By grouping circles into orbits you have a as much or as little granularity as you desire (just create an orbit for each circle if you wish). For users who use the feature for the first time, the first few orbits could have defaults of gradually-reducing visibility settings.

What do you think? Too elaborate? Would this take care of the 'Scoble Virus' well enough? Leave a comment here, or of course on Google+ with ideas and suggestions

A year in the life of a jet-setting innovator

Tue, 05 Apr 2011 16:01:18 -0700

I've been flying around for the last year in aid of my latest project, and I just realised I hadn't documented any of it, so here goes...

I'm writing this with Trent Reznor's The Social Network soundtrack in the background (it helps me think and just felt apt). Do I feel like a budding entrepreneur on the brink of developing something amazing, sometimes. Do I feel like I'm the only one who understands the true vision of the thing We've been trying to devise, sometimes. Have I been working with a truly awesome and talented team throughout, definitely. Have I lived a great life thus far, no, We've been slogging our guts out, giving up our personal lives for the chance to make our project a success, but there have been smiles along the way. Where to really begin?

I might as well start at the beginning (I guess this is going to end up as another essay rather than a brief post). I love working for who I do, the projects I get given are always interesting, the people I work with are great, and I constantly feel like I'm doing things which make an impact into the products we sell, but the company (like many) has been going through hard times in terms of the recession and an increasingly aggressive industry, and the atmosphere at times is a little tough with people wondering where cuts will be.

In January last year (2010) there was an announcement that an innovation programme would be created, and a selection of people from around the company would be brought to Silicon Valley (Santa Clara, CA) for 2 months and would be given the chance to work on new product concepts around the topic of 'cloud'. There was a test, a set of questions aimed at getting an idea of whether we had the skills and ingenuity needed to make the programme a success. I recall a couple of questions about programming (what does this Go code do, why does this code crash and how would you fix it) along with a few about architecture.

I was forwarded the news item from a few different directions, nudging me to apply, but I didn't know if I wanted to leave my friends and girlfriend for such a long time. The California timezone isn't the most social for communications with Europe. Eventually, after putting a message on Jaiku & Twitter I got the suggestion "why not take Miia with you?"... genius!

So, on the last day of applications I sat down, quickly answered the questions and sent it off. Eventually got notified that I'd got through the first round, then a phone interview, then told I'd made it through, and away we went to California.

Now, The time in San Francisco wasn't the best for Miia, having a hard time to work remotely with the huge time difference, and not having any way to go more than 100m from the hotel room because of busy roads and motorways (bad hotel location), I feel really bad that I couldn't make her time there more exciting.

My initial feeling on arrival was mostly "I'm finally here, where all the companies I admire are", and our first drive down the 101 seeing the Oracle, Cisco and many other huge company office blocks, and the Zynga billboards (still don't 'get' their products) you could tell we were in the right place.

After the first morning of getting acquainted with the area, a little walk to a viewing spot of The Valley and some motivational speeches, we were set to work, with our brand new 15" Macbook Pros... count me happy!

What followed was 9 weeks of obsession... 60 hour weeks (at least), not including weekends, a constant reminder of the time running out thanks to a 'XX days left' countdown near the entrance. Every week having to show progress through the ritual of a 'Friday demo', this was Scrum taken to the extremes. The first week was fun, getting our feet, getting into the spirit of things and starting from scratch several times in terms of our vision. By week 4 we were all noticing how much time we were spending in the office, and how we weren't really experiencing the area at all. By the final week there had been people ill from stress, others falling asleep while eating... We had given our all, both physically and mentally.

That was last March-May, and the result was 6 service prototypes, 4 of which moved to the next phase: Productisation.

At the start of the next phase I was given the chance to be the lead for my project. The last 8 months have been exciting, stressful, irritating, draining, and productive. Sometimes individually, sometimes all at once. My first experience of managing a team (including several people who would usually be considered senior to me) has been very much a case of 'thrown in at the deep end', a team of 10 developers and 3 (then 4) marketing people.

The location for the last 8 months was Berlin. Fairly central, but having to travel every other week for 6 months wears a bit thin, not only personally, but for family and friends who never know where you are. In that time I've made 21 trips - that's 42 flights (a couple for personal trips), spent a total of 92 days in Berlin (while having seen next to nothing of the city's sights), and had approximately 3 weeks where my working hours were less than 45 hours. It's simply unsustainable, but we've done what needed to get the project made.

Splitting my time between the duties I had as Product Owner (in the Scrum sense) for the R&D team and the responsibilities I had in making sure the strategy and marketing message went in the right direction was very tough, and continues to be to this day. Something I have found, however, is that the developers require less management than marketing (at least in my case), even though there are more developers (I guess I'm lucky to have a talented team of developers) the strategy and marketing side of things is somewhat newer to me, so trying to keep the reins tight on those topics was a lot more of a challenge. I also attribute to that the fact that the developers (to some extent) have experience being customers of the kind of service we're trying to create, where the marketing team perhaps didn't, and were more experience with selling traditional products our company makes, which is hard to compare with.

The result of the last 8 months is what I would call a good beta product release. I mean that as a compliment, I think the amount of progress in such a short time (compared with our company's usual time-scales) with a pretty small team is incredible. I think we have a viable product that's competitive in our market, and has the potential for greatness. In short, I think we've caught up with our competitors in technical terms. We still have a little way to go with the marketing side, but the progress in that area has been amazing, considering the traditional background of the team.

So, that's a lot of build-up, and a quick overview of my time so far. I may go into more details about certain aspects in different posts.

My advice for innovation programme managers

Your primary duty is to remove obstacles of any kind from the people who are creating the valuable assets. Remember that in such a big business things get slow from additional processes put in place to ensure people don't take advantage of resources because things can't be micro-managed so easily from higher-levels. Contrast that to the fast-paced world of a startup, where financial, resource and strategy decisions can happen overnight, and frequently. One example to make you think... how long in your organisation would it take to get a bank account and Paypal account set up? Startups would take 10 minutes, but add in SAP, SOX and layers of legal and finance & control personnel and the inevitable delays happen.

Don't micro-manage over each team's strategy until it's mature. Be an advisor, by all means, but do not for one moment pretend that you have all the answers or that you know the ultimate direction any one of the projects should be aiming for. This, to me, is a key element of a startup, the [usually] fresh talent sees opportunities in some strange places, and sees a path to riches that can't always be grasped by others. Take for instance the latest startup Colour/Color. The investment by Sequoia Capital of $41M was made not on the current product or one of their visions, but that of the people that have that vision, there is a lot of trust in that relationship, and that trust is the same thing you have to have for your budding startups, don't smother them.

Give your investment time to find it's feet. There's a great quote in The Social Network, said both by the Mark Zuckerberg and Sean Parker characters in response to the Eduardo Saverin character's comment/question about monetising the site (Facebook).

"We don't even know what it is yet. We don't know what it is. We don't know what it can be, we don't know what it will be, we know that it is cool."

You have to find a way... and don't think I have an answer to how, but you have to have find a way for the projects you start to live long enough to be successful. In businesses that are in a lull or a panic stage of trying to reinvigorate the company, it's tempting to make harsh judgements on short-term performance and usually based around the revenues and profits. If the majority of today's successful startups had been started in such a culture, they would have been culled before ever making it to the stage where money actually begins to flow. This is, in my opinion, the area which needs the most consideration before the innovation programme gets started... make sure you set the expectations of the investors (whether internal or external) that things aren't going to be instant... No-one likes a rushed product, and when that's a service it'll be dead in the water, with other competitor startups picking at it like vultures for the novel features they wish to implement later.

Be as open as possible... publicly. Open the gates for the teams to be public about their projects as much as they want to be. Allow them to blog about issues they're having, or things they're thinking about. Getting outside opinions early is always a good thing. Of course there's a risk your competitors, but that's more incentive to be quick... in most cases you're probably catching up to the market rather than being innovative (in one way or another), and you need to get your visibility to the same state as your competitors by the time you get to the same level of maturity as they are, so it's a gamble. If you think you have unique features leave them for the big launch day, but for the 'table-stakes' features, be open and get the word out.

Open source stuff if you can, or at least contribute to other open source projects. This is easy when concerning fundamental infrastructure that you rely on but doesn't perform any particular 'business logic' for you in itself. Just look at Twitter's open source page for examples of things you could release. Yes it could help your competitors, but the chances of you running the same architecture as your direct competitors is minimal, and on the plus side it'll get your name into the development community as a good contributor, and in the long run I think that'll pay dividends when you reach the limits of some of the components you come to rely on.

Installing Xubuntu Lucid on a Viglen MPC-L

Thu, 02 Sep 2010 11:28:22 -0700

Installing Xubuntu on a Viglen MPC-L isn't easy, and what we had to do didn't follow exactly the guide we used, so here's the differences.

We used Tony Whitmore's blog post as a guide for installing Xubuntu on Miia's new Viglen MPC-L machine, and although it was a useful start, I think some of the changes between Ubuntu and Xubuntu, or some of the installation disc updates to Ubuntu Lucid (10.04) mean a slightly different process needed to be followed.

Downloaded the Xubuntu i386 desktop ISO.
Turned it into a bootable USB stick using the "Startup Disk Creator" program in System Tools.
Booted the MPC-L off the USB stick. (N.B. It will only boot from USB sticks inserted into the rear USB sockets.)
At the splash screen, selected the advanced boot options (F6), and selected expert mode and when prompted for the boot string, type in "pnpbios=no noapic acpi=off" to the end.
Install as normal.
At the end of the installation procedure, at the "reboot" prompt, reboot (it's the only option), but keep the USB stick in - The system won't boot on it's own right now, since it's got the wrong kernel.
Go into the LiveCD mode (the top boot option), remembering to give the same boot options as before.
When you get to the desktop, open a terminal.
Since you've rebooted, you now need to remount all of the partitions the installer configured into their place within /target. We managed this by:
sudo fdisk -l - Find the relevant partitions (probably sda...)
sudo mount /dev/sda1 /target - Do the same for any other partitions you created (eg. /target/home)
In the terminal session I set up a chroot to install a suitable kernel:
sudo mount -o bind /proc /target/proc
sudo mount -o bind /dev /target/dev
sudo mount -o bind /dev/pts /target/dev/pts
sudo mount -o bind /sys /target/sys
sudo chroot /target
You are now inside your newly installed version of Xubuntu, almost like a virtual machine. It only exists within that terminal window.
Make sure your DNS settings are correct, otherwise you'll have to edit your package sources to use IP addresses.
Installed a kernel: sudo apt-get install linux-386
Once the kernel has installed, edit /etc/default/grub and add the same boot options as before to the GRUB_CMDLINE_LINUX_DEFAULT line after "quiet splash ..."
sudo update-grub2 to commit your changes to the grub config.
Exit the chroot and terminal (type exit twice). Then reboot, taking out the USB stick.

Hopefully this helps with a 'smooth' install. Once it's booted into the working system you can uninstall the linux-generic package, since you're using the linux-386 kernel.

If I Designed It - Android Browser

Fri, 02 Jul 2010 14:28:56 -0700

The start of (hopefully) a series of posts describing little user experience/design tweaks I'd make for different objects/applications/services. Starting with the Android browser and Google login

I've been meaning to start a new blog (yes, another one) to start gathering my thoughts about user experience, usability and design of things I use every day, mainly of a technical variety, but about anything from mobile applications and web services to toasters and TVs. Some might be big things, others small tweaks that would make my life just a little more pleasant.

In case there are any industrial/UX designers at Google or other huge company, let me just say, the ideas I'm publishing here are there for the taking under the same license as all my other posts, Creative Commons, except these will be licensed without the non-commercial restriction, so feel free to take the idea and build it into your products.

The real post

This first post is centred about my mobile, Google's Nexus One. To be more specific, it's about Android's bundled Browser when used with web services requiring a Google account to log in.

My suggestion is small, but I think it would improve the user experience. When I choose to log into a web service using my Google credentials, I'd like the browser to trigger an intent which would cause a dialog box asking me whether to use the credentials already stored in my device. The browser would then take back control and the web service would load the logged-in page, as if I'd returned from the Google login page.

Another bonus of this could be an 'always do this' checkbox on the dialog which would then automatically process the login without showing the Google login page and without even showing the dialog.

Further bonus points would be awarded if that 'always log me into this service with this account' type of option would store an indefinite session handle (securely) and use that to keep me logged into services, without the need to even click the 'login' button on the site ever again. The options for forgetting the logins (think like OAuth tokens) could be accessed through the normal Accounts settings.

Think the idea's good/bad? Think I've missed a trick? Express your thoughts in the comments

Android App: Conference Call Dialer

Fri, 04 Jun 2010 15:34:56 -0700

After a week of my first android application being in the Market, an introduction to the app itself.

My application has gotten off to a great start in the Android Market. Over 100 downloads and over 65% active installations. So, what does the app do?

Well, it's a pretty simple application in the grand scheme of things. It just stores sets of numbers in a database, displays them as if they were contacts. The numbers relate to conference room numbers and PINs, and with a single tap on an item in the list, the phone starts dialing the preconfigured conference switchboard/bridge number and types in the right numbers to access the room, including pauses and hash key presses.

I haven't taken any screenshots of the app, since it's not very pretty, and it really is pretty simple, but I may add some more with later versions if I add some more complex elements.

Like many small applications, I made it to 'scratch my own itch', so that I wouldn't have to add several 'voice conference' contacts to the standard Contacts app, instead I could keep a completely separate list dedicated to conferences.

You can get information about installing the application over on my new Android microsite.

For anyone wondering, the test conferencing system (which is the only one I can currently say it works for consistently) is Elisa Finland's voice conference service. The numbers are completely customisable though, so don't let that stop you trying it out, it should work fine with your provider too.

The code is released as open source, and you're welcome to take it, use it in any way you like, and if you make any good additions to it, let me know and I'll put them in the official release. If you don't know how to code, you can still suggest new features, or tell me about any bugs you might encounter

Experiences coding for Android

Mon, 31 May 2010 16:11:48 -0700

Having had a Nexus One for about a month, I've just released my first small application and now I'm reflecting on the experience.

After being a Nokia fan for over 10 years (and employed by them for a few years too), it was a sad day when I retired my E71 to being my new 'backup/roaming phone'.

As I mentioned in a previous post, I was confused about which direction to go, but having played with the Nexus One my girlfriend got free as an attendee of Linux Collaboration Summit 2010, I couldn't resist... the draw of the applications was too great.

Having battled with the Maemo and S60 development kits before to no avail apart from a couple of days of headaches while attempting to follow the tutorials step-by-step, I thought I'd never get to grips with mobile coding, especially as I hate Java too.

Enter Android, a Java-only development environment that I've actually been able to get stuck into. Ok, I may have been eased into it slightly by having 2 months in the San Francisco Bay Area on a work project, spending 2 months picking up Java and OSGi architecture, but I'm still surprised I've managed to be so productive with Android's development kit.

I hope I'm not misunderstanding too much when I say this, but the concepts of OSGi that I picked up while in America have helped me appreciate the modular approach of Android development, and looking at many of the applications I've installed, it seems strange to me that so many applications have implemented the same core tools (eg. Barcode scanning), even if they're using the same library (eg. ZXing), rather than just calling for the central application to do it's job and pass back the information it gathers.

Now, as far as the documentation goes, it's a little step up from the standard Javadocs I used to see, but it's still not amazing. For a relative Java newbie it's sometimes hard to tell how exactly I have to use a particular piece of code, of how to get hold of the data I need to pass in as parameters (eg. contexts), and occasionally not realising that I need to implement an 'on...' method within a particular class. Once you've worked your way through those hurdles though, it's pretty surprising how productive you can be.

I first started with a couple of harder pet projects (having decided to skip the tutorials all together), got stuck pretty quickly in web-services stuff, and finally decided to do a more simple application to ease myself in slowly. In around 3 evenings, using the Notepad tutorial as a quick-reference now and again for the basics of SQLite usage, I've managed to build and publish my first Android application, but that'll be mentioned in full in my next post.

After my limited experience of attempting to begin developing for S60 (Java and C++), Maemo, iPhone and Android, I would say that Android is one of the quickest things to get up and running with. Couple that with the cheap $25 one-off fee to enter the market, and you've got a winner. Maemo (now MeeGo) would come a close second, but the limited amount of non-Linux development tools kind of lets it down... not that I'm advocating Windows for development, It would just be nice to be able to develop on my Macs rather than having to boot into Ubuntu.

I've created a new section of my site, dedicated to being my little slice of the Android Market, where I can place more details, more screenshots/screencasts and details about the open source applications I develop, so I welcome any critiques, reviews, comments and suggestions for things I should build next.