Zedray

Naked Capitalism: How Germany Achieved Stable and Affordable Housing

Very interesting Naked Capitalism post on the huge difference between Germany’s property market and that of the United Kingdom.

Two comparable countries with radically different systems, one of which is designed to make property older, smaller, scarcer, and totally unaffordable.  I now live in Germany.

Awesome California Monterey Peninsula

Five cool things about a couple of days driving around the Monterey Peninsula…

Coastline
Gorgeous views.

Whales
Go see the Monterey Aquarium they say, but isn’t May the best time to see these creatures in the wild?  Get a boat and have a “Bunny Hugger” Marine Biologist provide a running commentary, as Humpbacks and Killer Whales popup and make their appearance.  Remember to dress appropriately!

Seals
Loads of them just sitting on the beach having a good rest after a hard nights fishing.  Stand behind the fence and watch out for the cute babies waiting for their mothers.

Giant Redwoods
Tall trees, very old…  Here before you were born, still here long after you’re dead.  Great place for a guided walk and a quiet sit down.

Surfers (of various kinds)
Crazy guys playing hard and fast with nature, making dangerous look cool.

Awesome Mountain View

Three cool things about driving past Mountain View… Computer History Museum
Find out why they call it Silicon Valley.  See who the first computers were, with what they were replaced, and how we got to where we are today.  Learn how US government spending fostered various computer revolutions.  Take the Geek tour and get an inclusive T-Shirt and pin.

Google (or just about anyone’s) corporate head offices
See the colourful campus bikes and logos surround expansive (but otherwise standard) red brick corporate offices (triggering fond memories of my time at Sun).  Or visit Apple, which is less than ten miles away down in Cupertino.

SFO Airport
Not exactly in Mountain View, but I only drove this way while driving back to get my flight.  There just wasn’t enough time to do everything.  Maybe I’ll get to do this again next year?

Google I/O 2011 Highlights

Location
May 10-11, 2011 @ Moscone Center, San Francisco. There was far too much content at the conference this year for me to take it all in.  Even to follow just the Android track would require being in three different places at the same time.  Hence, this post is just a brief summary of what I did + found interesting while I was there, with links to the relevant session videos on YouTube where available

Bootcamp (Monday)
Boot camp is a much smaller warm up event (at a different location), giving students and developers a chance to get setup on key technologies before tackling the more advanced stuff at the main event. Pros

• Real lab tutorials to get your hands dirty on working code.

Cons

• Googlers are briefed not to announce anything new.  Resulting in Q&A sessions full of frustrating holes.

Highlights

• Welcome “Don’t try and boil the ocean” and “Making the most of I/O” speech.
• Avoided “Beginner’s Guide to Android” (I hope I know this stuff by now) and went to “Intro to Google APIs” instead.  Google have over 100 APIs and now offers a standard way to access them online and in Android compatible Java code.
• “Google TV, the New Frontier for App Development” came with tips for testing Google TV apps in the current emulator.  Google TVs are a promising new class of Android device, although the product rollout will be America centric for some time with free development devices only available to US based developers.
• “Android Best Practices for Beginners” - Lots of UI tips and tricks, always a good recap (even for old hands).
• “Introduction to Honeycomb” lab session on migrating the Notepad application to the new Honeycomb UI (i.e. using the new Fragments and Action bar API).  Very useful tutorial as we all got our hands on proper Honeycomb hardware the very next day.
• “Getting Started with GWT & Google App Engine” - GWT offers a Java friendly method of building web apps (which are becoming more mobile friendly), and GAE offers a well supported tool chain for developing back ends (for both Android and GWT based apps).  This is a powerful combination for those of us who would like to build our products end-to-end using Java code (i.e. Android/Java clients connecting to Java servers, hosting Java based Websites).

Google I/O Day One (Tuesday)
5,000 students, developers and press crammed into San Francisco’s Moscone Center West, offering a busy conference schedule, sandboxes and office hours with developer advocates. Highlights

• Watch the day one keynote, as it’s almost exclusively Android announcements.
• “Honeycomb Highlights” - Essential viewing for anyone developing on Android Tablets.
• “Android Protips: Advanced Topics for Expert Android App Developers” - Reto Meier (yes the author) on stage explaining how to make our great apps awesome and more tablet friendly.
• “Don’t just build a mobile app. Build a business” - Summary of advertising on Android, regretted attending because next door they were giving out free USB developer kits.
• “Fireside Chat with the Android Team” - Long Q&A session with the heads of the various development teams.  I asked a question near the end and got brushed off as the answer was too commercially sensitive.
• “Android + App Engine: A Developer’s Dream Combination” - Google eclipse plug-in now provides end-to-end support for GAE, GWT and Cloud to device push messaging.  Very serious piece of kit, and all for fee.  Essential viewing!
• “After hours party,” with Ice cream, pinball, robots, branded cookies, flying cars, and a loud rock band.

Google I/O Day Two (Wednesday)
Highlights

• Day two keynote was chrome and web apps focused, with the “Mighty Eagle” of Angry Birds on stage.
• “Android Market for Developers” - Loads of new announcements, and I burned my lunch hour by staying afterwards for an extended Q&A.
• “Designing and Implementing Android UIs for Phones and Tablets.” Essential viewing, but the session was full before I arrived (I was stuck in lunch queues) so I attended “Optimizing Android Apps with Google Analytics” which contained little new information.
• “Evading Pirates and Stopping Vampires Using Licence Verification Library, In-App billing, and App Engine” - Helpful guide to securing your applications and back ends, and how to turn unscrupulous users into paying customers.
• “HTML5 Versus Android: Apps or Web for Mobile Development?” - Google are big into HTML5 web apps and offer tools for doing both web and native Android client development.  This was a great guide to doing dual development on the Google tool chain, along with the advantages of both methods.  Recommended viewing!
• “Taking Android to Work” - A look at the (currently limited) support in Android for securing the entire device to access corporate data.  You’ll see me at the end acting as a user advocate, asking for a secure mode so I don’t need a password lock screen on the weekend.

Much more session videos can be found here. Free stuff

• T-Shirts: Bootcamp (Green camouflage + Bootcamp logo – Google Employees got cooler White camouflage) and Google I/O (tasteful dark blue + Google I/O logo, with white Morse code puzzle on the back).
• I’m keeping my Samsung Tab for development, but gave away the Verizon 4G hotspot (with three months of data) to an American college, as the kit works only in the USA and he was the person most likely to make use of it.

Awesome San Francisco

Five cool things about a weekend spent running around San Francisco…

View outside my hotel window
With a 9 hour time difference it’s easy getting up early on Saturday morning and take in the view of down town San Francisco from Hotel Nikko.

Municipal Railway (i.e. the Cable cars)
Home to an amalgamation of Cable Cars (slightly less crazy than the ones in Lisbon), historic Street Cars (classy) and Trolley Busses, representing a hundred years of living transportation history.

Fishermans Wharf
An American Submarine (USS Pampanito), Seals barking on the harbour, anti-Obama political campaigners, and a soup + bread lunch at the Boudin Bakery to take it all in.

Golden Gate Bridge
Taking a boat tour from Fisherman Wharf, directly under the bridge and then back around Alcatraz island.  May was very windy, but great to get a photo in front of the flag.

California Academy of Sciences
Situated in the enormous Golden Gate Park, featuring an indoor rainforest (watch out for the butterflies), aquarium (beautiful), penguins (in too small an enclosure), all digital Planetarium (simply breathtaking), Global warming exhibition (how much jet fuel did I use this week?) and an Albino crocodile.

Google I/O 2011

For the first time ever, I will be attending the Google I/O (plus warm-up BootCamp) event in San Francisco. I am looking forward to getting my hands on a usable “Honeycomb” Android Tablet (maybe as a freebie?), get a chance to try out Google TV and probably learn as much as I can about GAE and GWT.  Anything else that happens when I’m over there will be a bonus. Now lets see how I cope with the jet lag.

Global Android Activations, Oct ‘08 - Jan ‘11

Data visualization of global Android device activations from October 2008 to January 2011.

Unstable Walking Robot

As an inventor I’ve always wanted to program a robot to walk, but have never seen hardware capable of providing the power to weight ratio required to replicate the inherently unstable human walking motion.

By unstable, I’m talking about robots without the big blocky feet that stop them from falling over when you switch them off.

At about 1:40 the robot slips, rather than loses balance.  I think they should replace the blades with a “hoof” design, using Bocks (a German invention) for inspiration.  Source of video PlasticPals.com.

Localising (or Localizing) the Last Call Widget for Android.

The Android Market is a worldwide phenomenon, and I want to make my application more accessible to my users wherever they come from. Who are my users? Unsurprisingly for software written in English, three quarters of my users have their Android devices set to English locale.  What surprised me was how many English locals existed (46 in total), including those where English is a minority or foreign language (e.g. code “en-DE” indicates a device set to show English text, but to use say German currency and conventions). In Asia (a continent I have never visited), I have a strong Korean, Chinese and Japanese user base, while German, Spanish, Russian and French are the most represented European languages.  Though interesting, I am going to ignore the 31 languages less popular than French in my translation activities for now. How to localise? Android provides its own framework for separating texts (called “Strings” by developers) and resources from application code.  This makes it easy to integrate Android software into existing content management systems built around translation.  While I’ve written a few of these systems in my time, I was looking for a company that offered tools and translation services online to provide scalability and to help with independent projects. [Android Application Resources, Localization and Tutorial] Tool review - ICANLOCALIZE This is one of many websites offering online translation services, though I chose it because it offered native import of Android formatted “string.xml” files, upfront pricing and a straightforward workflow. [ICANLOCALIZE.com site and Android Localization Tutorial] For my first test, I chose to commission a German translation, as it allowed me to easily review the results and judge the quality of the translation myself.  Screenshots of the actual translated work can be seen here. Likes:

• It took about 5 minutes to sign up and create a basic Last Call Widget project ready for translation.
• Duplicate strings were highlighted by the tool, helping me optimise my strings and save money.
• CMS let me add my Android Market listing info and other meta data.
• CMS let me add my own translations.  Useful because 21 Strings were ripped off from the Android open source project where they come pre-translated.
• My 49 Strings cost $10.85 (or 8.19€ in my local currency), and was completed the next working day.

Dislikes:

• Resource importer did not remove XML escape characters.  This made my translations look messy in the CMS, although the translator was smart enough to work this out for herself and left them in place.
• Resource exporter should not include the untranslated (i.e. default English) strings, as Android handles this during runtime by showing default Strings instead.  Having duplicate English strings across multiple files only makes my APK fatter.
• Resource exporter should output XML parameters with double quotes instead of single quotes.
• It’s not clear how translator ratings are calculated.  Looking at the site I didn’t see many people with less than a 5 star rating, even those with no recommendations by clients.  This makes it difficult for a customer to choose between translators.

What I would like to see:

• My software is free but not open sourced, and I regularly get offers of translation from end users and app store representatives.  What I would like to see is a Wiki like interface that I can point these people at, so they can easily update the Strings themselves.  Note: This may be comparable to the “Private translators” feature which I am yet to try.
• Software versions change, and I would like a way to tag translations to specific versions of my software.  This would allow me to support older (or branched) versions of my software and give me some of the flexibility I am used to while developing with GIT.
• Generating, and then regenerating screenshots for review is a time consuming process.  Hence I would like to see a screenshot maker script for Android, probably implemented as an add-on in the test project.

What I was freaked out by:

• I know that there is a lot of demand from end users to localise my software, but I was shocked to receive a complete and unsolicited German translation of my application from an end user on the same day that the ICANLOCALIZE translator turned around her work.  It was fun to compare the two for differences, but the paid service was of overall higher quality.  Strange coincidence.

Conclusion Translating an application is expensive, and Last Call Widget isn’t currently set up to make any money.  Right now I am interested in translating for some of the high value languages, and enabling motivated users (of which there seem to be many) to translate the app themselves.  Having a tool chain that supports localisation will be invaluable to future commercial ventures. Translation ads a financial cost to every String in the application, discouraging UI changes, and pushing designers towards using symbols rather than words to convey messages whenever possible.  Ideally translation should occur at the end of a software project, but should not be considered as an afterthought. I’m still working out how this applies to agile software development. Note: Just to destroy any aura of impartiality in the above review, I found an “Affiliate link” feature in the control panel and have swapped out all the links in this post.

Multi-platform UI Guidelines For Mobile and Tablet Application Design

The most complete set of UI guidelines I’ve seen to date, curtsey of Maximiliano Firtman.