Sunday, February 8, 2026

Letting Gemini Drive My Rover

 Letting Gemini Drive My Rover

LLMs have had visual capabilities for a while now, with the general ability to understand what they’re looking at. However, while this semantic understanding has always been impressive, they have demonstrated very poor spatial understanding, with earlier models struggling with very basic tasks like drawing bounding boxes or giving accurate pixel coordinates of what they see.


This is starting to change and both Qwen3 and Gemini 3’s releases last fall highlighted their new “Spatial Reasoning” capabilities - not just understanding what’s in a scene, but how these objects relate to each other, how they are placed, etc. Gemini 3 in particular shows impressive ability to draw trajectories describing movement from one place in a scene to another. How well does this really work in practice? Can Gemini drive a rover?

This is interesting because LLMs can be a great complement to existing ROS2 robotics tools. These tools have a strong understanding of geometry - they can see the world in 3D (thanks to LIDAR and depth cameras), they’re aware of how big the robot’s body is, they can see obstacles and plan paths around them etc. But they’re also kinda blind - scenes are geometric and existing models only offer basic and brittle understanding of the world. LLMs on the other hand, lack any sense of scale, size or geometry, but have great semantic understanding and strong reasoning capabilities. It’s a match made in heaven!


I have a small tracked Waveshare robot powered by a Jetson Orin Nano 8GB and using an OAK-D Pro depth camera. The camera captures RGB-D images, where each pixel has a colour and depth, allowing the robot to see the world in 3D. To test Gemini’s capabilities, I wrote the following program:

  1. The user enters an arbitrary target that’s in the robots field of view. This can be as simple as “Blue Ball” or as complicated as “orange lego bus on the left side of the red chair”.

  2. A request is sent to Gemini to generate a trajectory from the robot’s current position to the user’s target. The prompt includes instructions on what a good trajectory looks like, what to avoid etc.

  3. Gemini returns the trajectory as a set of (x,y) coordinates in JSON format. Because the robot has a depth camera, it is able to project these (x,y) coordinates into (x,y,z) coordinates using the depth info and the camera’s intrinsic parameters.

  4. These (x,y,z) coordinates are sent to Nav2 (ROS2’s navigation tool) as a set of waypoints, including calculating the correct robot orientation for each waypoint. Nav2 can reject this trajectory if it is not traversable based on it’s own understanding of the 3D scene, obstacles, etc. Rejected trajectories are potentially valuable fine-tuning data.

  5. Nav2 executes the trajectory but using its local planner keeps an eye out for obstacles and stops the rover if a new obstacle is detected, so if a person or pet moves in front of the rover while it’s executing it’ll stop safely.



So how well does this work in practice? Not great, but not terrible. The whole setup works as intended, the trajectories Gemini generates place the robot near the target, but they’re not sensibly spaced out, and it doesn’t do well with far-away objects. I suspect the robot's type or low perspective 1 foot off the ground might be uncommon. In addition, lag is a major problem - it takes about 30-60s for an API call so having this run continuously would be both slow and expensive. 




There’s two interesting follow-ups from here:

  1. Put this in a loop and have Gemini try to achieve an objective, like map out a room by itself.

  2. Fine-tune Gemini 3 Pro with a collection of good trajectories we’ve seen, improving its performance. We can use Nav2’s geometric understanding to fix and clean up trajectories as well - for example enforcing 50cm spacing between waypoints. This effectively creates quality semi-synthetic training data.

  3. Distill Gemini 3 Pro’s capabilities into Gemma3 4B or Qwen3 4B. These vision models are small enough to run locally on the robot’s Jetson at several hertz, getting rid of the lag and the need for an internet connection.This may only work well for scoped tasks like indoor navigation.



As we’ve seen with Claude Code and other coding agents over the last year, giving LLM agents robust tools (3D scene understanding, obstacle detection) and sensible harnesses can give them impressive new capabilities. One reason you might want to use LLMs directly instead of Vision Language Actions models is that when paired with a map, tools like ROS2 can implement existing navigation algorithms like covering an area and can effectively keep track of state. VLAs are largely reactive, keeping only a few seconds of history, so keeping track of state has to be done in an external memory system regardless.

Thursday, February 5, 2026

Keep Your Voice

If you care about your voice, don't let LLMs write your words. But that doesn't mean you can't use AI to think, critique and draft lots of words for you. It depends on what purpose you're writing it for. If you're writing an impersonal document, like a design document, briefing, etc then who cares. In many cases (scientific papers, legal documents) you already have to write them in a voice that is not your own. Go ahead and write these in AI. But if you're trying to say something more personal then the words should be your own, AI will always try to 'smooth' out your voice, and if you care about it, you gotta write it yourself.

Now, how do you use AI effectively and still retain your voice? Here's one technique that works well: start with a voice memo, just record yourself maybe during a walk, and talk about a subject you want, free form, skip around jump sentences, just get it all out of your brain. Then open up a chat, add the recording or transcript, clearly state your intent in one sentence and ask the AI to consider your thoughts, your intent and ask clarifying questions. Like, what does the AI not understand about how your thoughts support the clearly stated intent of what you want to say. That'll produce a first draft, which will be bad. Then tell the AI all the things that don't make sense to you, that you don't like, just comment on the whole doc, get a second draft. Ask the AI if it has more questions for you, you can use live chat to make this conversation go smoother as well, when the AI is asking you questions, you can talk freely by voice. Repeat this one or two more times, and a much finer draft will take shape that is closer to what you want to say. During this drafting state, the AI will always try to smooth or average out your ideas, so it is important to keep pointing out all the ways in which it is wrong.

This process will help you with all the thinking involved being more up-front. Once you're read and critiqued several drafts, all your ideas will be much more clear. Then, sit down and write your own words from scratch, they will come much easier after all your thoughts have been exercised during the drafting process.

Sunday, March 26, 2023

A Stadium Full Of Ancestors

You are sitting in the centre field-level front-row seat of a large football stadium. On your right is your mom, and beside her, your grandfather. You know them well, you say hi. But beside him is his mom, and her father, and his father, and his mother, and her mother, and her mother, and her father, and his father, and on, and on, and on - an uninterrupted line of your ancestors snaking their way all around first row, then the second row, then the third row, and on and on until they fill the entire stadium. 

You don't know these people, but at first they look very familiar, except they wear funny clothes. They're obviously conscious and intelligent and deserving of legal personhood just like you. But you look a few rows up and they start to look off, kinda weird. Whether Neanderthal or Denisovan, they're not quite like you any more. The further up you look, the less humanlike they look, until you look at the top row and see your great^100,000-grandmother Lucy. She's bipedal, but not human anymore. If you saw her in a zoo rather than at the top of the stadium, you would never think that she is conscious, or deserves the same legal rights as you.

So where in this stadium did intelligence and consciousness arise? Is there a single ancestor you could plausibly point to and say, "This person deserves legal personhood, she's conscious, but her mom, no she is not a person". It's impossible, the boundaries of intelligence are too fuzzy. The best you can do is point to some rather large group and say that somewhere in there, the rate of change added up enough to make some kind of difference.

As we wonder whether an AI is "alive", when they will become conscious or intelligent enough to deserve legal protection, it's useful to remember that the answer will probably be at least as hard. A definitive answer may well be impossible, it will be fuzzy and we'll reach broad consensus slowly.

Monday, September 28, 2015

How Cheap Can Autonomous Cars Get?

Autonomous cars are coming and everybody thinks they'll be a pretty big deal, but it's impossible to predict what their impact would be exactly. Today they are billed simultaneously as the saviour of our congested, car-dependent cities, and a job-killing, life-destroying tool of the global technocapitalist class.

To help us think about their impact, let's consider how cheap self driving cars could be. We'll use the simple metric of money per kilometre and make the following assumptions:

  • The year is 2039 and full Autonomous Cars (ACs) have been shipping for over a decade.
  • All new ACs are electric, with an efficiency of MPGe (5km/kWh).
  • The autonomous drive systems have been around for a while and are commoditized, like ABS or Traction Control systems are today. They add $ to a vehicle.
  • Electricity costs $/kWh
  • Our car costs $, comes with a km range, and the 100kWh battery pack has charge/discharge cycles.
  • Insurance costs $/year and maintenance is $/year. The life of the car is
  • The residual value after end of life is $


Given the above, our battery usable life is:

1000cycles * 500km = 500000km

The running costs of the car are:

5 years * ( + ) + 500000km / 5km/kWh * $5/kWh = $xxxx

So the total cost of this car is:

$xxxx + $ + $ - $ = $

Which gives us a total of:

$ * 100 / km = cents per kilometre.


Feel free to play around with the assumptions. After playing around a bit, we can see that the biggest impact, apart from the price of the car itself, comes from the quality of the battery - a larger battery with a longer life (recharge cycles) is more important than cheap electricity or a marginal improvement in efficiency (milage). This makes sense, as a car with 50 more recharge cycles will give you significantly more milage for the same buck.

Using the default assumptions, we get a price of 14 cents per km if you ride in this non-luxury, mid-size car 100,000km/year. Assuming this car is part of a taxi service and we add some profit, we can expect to pay $2 for 10km, which is quite significant as it is even cheaper than most public transit systems today.

Thursday, February 7, 2013

What Comes After Services? Interpretation

I've been reading the book Regenesis by George M. Church, which provides a great overview of where the biotech industry is heading by an author with ample academic and entrepreneurial experience.

In one section, Church describes the evolution of genetic research over the last several decades - how scientists went from doing everything manually to using machines and how much more productive they became. He ends with:
So in summary, the descent of man (the devolution of research persons) went like this: (1) DIY. (2) Buy parts. (3) Buy kits. (4) Buy machines. (5) Buy services. (6) Buy interpretation. 
This immediately struck me, not only because of its resemblance to the evolution of the computer and many other technologies, but also to a very important aspect of startups: how to make money by offering customers value.

Generally speaking, your profits will be proportional to the value you offer your customers and you'll pull ahead of your competitors by offering more value. At the same time the commoditizing nature of technology means that what's valuable and profitable today will become ordinary and cheap tomorrow. The challenge for startups then is to move up this value chain, disrupt competitors stuck on the lower rungs of the ladder and reap the profits.

Here at Kytephone, we make an app to turn an ordinary Android into a kids phone with parental controls. This lets us give parents peace of mind by offering them a service that lets them locate their child, see who they've been talking to, which apps they've been using etc. While parents certainly appreciate our service, what they really want is someone to tell them specific, important information - did my child get to school safely? Are they being harassed by someone? Are they spending too much time on Facebook? In other words, parents want an interpretation of their child's data to assuage their fears and worries.

Our challenge then is to give parents timely, important information about their children without them having to do anything. And bonus points for not asking for things back, like "Where does your child go to school?" While it is very hard for computers answer such questions, we are surely heading that way. We can see this not only in the Machine Learning boom, but also high-profile effort like Google Now or IBM Watson.

Tuesday, November 27, 2012

The Efficiency Index

I've always loved the idea of indexes - a collection of securities that make it on and off a list based on a well-defined set of rules. As I tried to image what a hypothetical "Drashkov Index" would look like, I quickly realized that all the companies I would put on there had one thing in common - if successful they would make the world a far more efficient place.

I believe that for the foreseeable future (the next two decades at least), the world will not see any form of cheap energy. Consequently, we won't experience anything resembling the cheap-oil fueled growth of the post WWII era. Today Americans make up about 5% of the world's population, yet consume about 25% of its resources. With billions of people striving for a Western standard of living, demand for energy will be insatiable. At the same time, the increasingly obvious effects of climate change will make more people receptive to treating and pricing carbon as the pollutant it is.

If we accept a world of high energy prices, the only way to grow and develop is to make our world a far more efficient place and in a way that is much different from merely optimizing our existing products and processes. To illustrate the difference, consider a few examples:

  • Marc Andreessen famously said that "Software is Eating the World". By its very nature, doing tasks in software is far more efficient than doing them in hardware. Writing an article on a laptop and publishing it online is far more efficient than using a typewriter, the post office and getting it printed on a pile of dead trees.
  • The mechanical parts and motors in electric cars are efficient in a way ICE engines and drive trains can never be. Tesla's Model S - a large, heavy luxury sedan - is considerably more fuel efficient than any econobox on the market today.
  • 3D printing / Additive Manufacturing is inherently a much more efficient way of building objects than the wasteful processes of today's manufacturing, which mostly involves starting with large blocks of matter and getting rid of lots of material.
  • Lab grown and artificial meat requires far less biomass and energy to make a pound of meat protein. While many people choose a vegetarian or vegan lifestyle, the majority of people in the world would like to enjoy the same meat and protein-heavy diet as westerners enjoy today. The only plausible way this will happen is through something as radically new and efficient as lab grown and artificial meat.

I hope that one day we'll see a cheap green-energy fueled economic boom, but for the forceable future, I think we'll be living in a world of expensive energy. The Efficiency Index - a collection of companies whose raison d'ĂȘtre is to make the world more efficient seems like a great investment. So, what companies would you put on the Efficiency Index?

Saturday, February 18, 2012

How To Make the 23" Android MegaPad

A few months ago I published a video showing me using my home-made 23" Android tablet, which got a bit of attention and made people wonder how it was made. A lot people made plausible guesses - that it was a staged video, that it ran android-x86, etc, but few made the right guess so I wanted to publish a how-to so anyone that's interested can make their own.

The core of the MegaPad is the TI PandaBoard - a $200 ARM development board which contains what are essentially the guts of any modern smartphone - a dual-core 1GHz CPU, 1GB RAM, GPU, WiFi and a host of connectors. The great folks at TI provide both Ubuntu and Android releases for the PandaBoard and it's fairly straightfoward to get one of the releases up and running. For the touch input and video output, I went with the Acer T230H, which was made for Windows 7 and uses optical-touch to provide 2 touch points with acceptable performance. This monitor has been discontinued by Acer, so I found it in Kijiji, but as we'll see, you can substitute with another suitable touch monitor.

The bit that makes it all work is this: pandaboard releases are made to work with a keyboard and mouse and will not recognize the Acer touchscreen if you merely plug it in. Luckily, Linux developers have written a touchscreen driver that works with the Acer monitor, so all we have to do is recompile the kernel with the right drivers and voila! We got ourselves a megapad. There a few more details. The touch driver that comes with the Gingerbread pandaboard release supports only one touch point, so in order to get dual-touch working as in the video, we'll have to patch the driver.

There are a number of improvements one could make to the MegaPad. The lagginess you see in the video is due to the fact that Gingerbread was never made to support 1080 at reasonable frame rates, however the folks at Linaro have been busy making an ICS release for the pandaboard, which you can check out here. I suspect ICS will run far smoother than Gingerbread. Moreover, one can use any size touchscreen, as long as linux drivers are available. I went with the T230H simply because it didn't require the big investment larger screens do. Now, without further ado:


Instructions

  1. First, get a PandaBoard from DigiKey, Mouser or any other retailer. I also recommend a Serial-To-USB connector, since you'll need to use the PandaBoard's serial connection as well as a very fast SD Card.
  2. Get an Acer T230H or any other touch monitor which has working linux drivers.
  3. install minicom or similar serial terminal on your laptop. The pandaboard does not how to boot itself, so you'll need to connect to the serial port and paste some bootargs to tell the bootloader where to find the kernel.
  4. Get everything working with a keyboard and mouse: You can follow the instructions here on how to download and put the binaries onto the sdcard. Essentially, the SDCard will be formatted with 3 partitions: bootfs where you put the boot loader and linux kernel, rootfs where you put Android and data where you can store media files. To boot up the board, put the card in, connect the power and start the serial console. When you see the fastboot countdown on the console, interrupt it by pressing enter so you can get a prompt, then paste in the bootargs found here.
  5. Once you have Android up and running on the pandaboard using a keyboard and mouse, we can recompile the kernel to get our touchscreen working.
  6. Set up your computer and get the tools you'll need to download and compile the kernel by following these instructions. Next, follow the instructions here to download and compile the kernel without any modifications.
  7. Once you have everything set up (and patched, as per the instructions), try compiling the kernel and loading Android on the Pandaboard with it. The compilation, which should take 10 mins or less, will produce a file called "uImage", which is the entire linux kernel. Take that file and copy it into the bootfs partition on your sdcard and start the pandaboard as before.
  8. If everything is working fine and you can compile and load your own kernel, we're ready for the modifications to get the touchscreen working
  9. In your kernel dir, go to arch/arm/configs/panda_defconfig and search for "#CONFIG_HID_QUANTA is not set", which should be commented out. Change the line to "CONFIG_HID_QUANTA=y".
  10. Recompile the kernel, load it on the SD card and connect the USB touch port from the touchscreen into the pandaboard and disconnect the keyboard and mouse. Once the boot is complete you should have a fully operable, albeit single-touch, megapad!
  11. To get dual-touch working, patch the quanta driver using this patch. You can find the driver under drivers/hid/hid-quanta.c. Once again, recompile and reload. You should now have dual-touch fully working.
Tips
  • The pandaboard may appear slow, which may be due to Android's inability to write to the /data directory. Put the SDCard in your computer, go to the rootfs (Android) partition and do "chmod -R 777 /data". I found that this made performance on my pandaboard acceptable.
  • The pandaboard needs a weird 5V @ 20A power supply and most 5V supplies won't work. I suggest merely plugging in the miniUSB port into your computer and power it the way you would recharge any phone or tablet.
  • Getting adb working is much the same as any other device. Add the following (SUBSYSTEM=="usb", ATTR{idVendor}=="0451", ATTR{idProduct}=="d102", MODE="0666") to your udev rules, restart udev and adb and you're good to go

If you have any questions and comments, you can check me out on Google+ here:

Happy Hacking

Wednesday, September 21, 2011

Android MegaPad - 23" Android Tablet for $600

I'd like to introduce to you a project I've been hacking on for the last few weeks - a prototype of a product I think will become a mainstream computing device in the next few years. As we all know, Apple brought touch computing to the mainstream in 2007 and showed us its potential. In 2010, they introduced the iPad and showed us that different screen sizes open up new possibilities but also demand different apps.

The Android MegaPad is then the next logical step - a modern touch-based computing device with with a screen size that will enable a whole different set of experiences. Unlike tablets, devices like this will make simultaneous use by two users a practicality and will let users more fully immerse themselves in apps and games. In the demo video below, you can see two apps that, while written for phones and tablets, nevertheless demonstrate the usefulness of such a device.


What makes this rather unique is that it was build using off-the-shelf components in my kitchen for less than $600, though it is not portable. On top of this commodity hardware, Android was used because its openness and flexibility make it the only modern touch-based OS that is able to be adapted for uses beyond what's currently available in the market. Stay tuned for technical details.

How To Save RIM

Last week was brutal for RIM . After announcing dismal quarterly results - profit down nearly 60%, revenues down 10% and PlayBook sales less than half of what was expected - the markets decided to punish them with a 20% drop in stock price.

RIM is going through a tough time right now. Like many other tech companies (for example, Apple in the 90s), years of neglect and complacency have led the technical foundations of the company to stagnate, ultimately affecting their ability to put out great products. Fortunately, it is still too early to write RIM off completely. Despite their troubles, they are still profitable, they have recognized their weaknesses and have acquired QNX and TAT to try and address them and perhaps most importantly, they command huge mind- and market share amongst young people. Should they be successful through this transition, they'll be one of the few companies competing in the mobile computing and communications market - a market which is likely to encompass nearly every person on the planet by the end of this decade.

One weakness they have not addressed however, is the lack of leadership at the top. Although it's understandable that RIM (like nearly everyone else) was caught off-guard by the iPhone's introduction in 2007, their inability to correctly asses the threat and create a competitive product over the last 4 years isn't. What they need then is someone with a wealth of experience in the consumer market and a keen eye for both hardware and software design - Jon Rubinstein.

Jon Rubinstein has one of the most impressive resumes in the tech world. After working with Steve Jobs at NeXT building their workstations, he was asked by Jobs to join him at Apple in 1997 and take over hardware engineering. Under Jobs' direction, Rubinstein was tasked with creating the iPod, which he did on an extremely tight schedule. After 10 years of numerous successes at Apple, Rubinstein left to become CEO of Palm.

In 2007, Palm was bleeding money, market share and talent and everyone expected them to go into bankruptcy soon. Nevertheless, Rubinstein managed to introduce the new Pre and WebOS - one of the most innovative and well-designed operating systems out there. Despite lacking the scale to become a major player, WebOS heavily influenced both Android Honeycomb and the PlayBook's OS.

I can't imagine Jon doing very well these days though. After HP acquired Palm with the intent of becoming a major player in the consumer space, a scandal and a change of CEOs led to a radical change of direction towards HP being an enterprise cloud provider with no interest in the consumer market. The cancellation of the TouchPad, Pre and the uncertain future of webOS imply that Jon has little, if any, future with HP.

This then, is a match made in heaven - RIM's still-solid position combined with Rubinstein's wealth of experience will increase RIM's chances of making through this transition and remaining a major player.  How likely is this to happen? Given the entrenched positions of both RIM CEOs, I think things will have to get much worse before major shareholders try and replace them. A shame then, given the current possibilities.

Wednesday, March 23, 2011

TetriNET is back as blockbattle.net - multiplayer tetris in your browser

Are you are current or former TetriNET or Blocktrix player? Then I have some excellent news for you - today we are finally taking the wraps off blockbattle.net. Blockbattle.net is essentially a very modern take on a a very fun, but abandoned classic game - instead of requiring players to download and install software, search for servers, ensure compatibility, etc, blockbattle.net implements the game entirely in the browser. It allows people to play without worrying about software and we've made a number of usability and gameplay changes to make it even better than the original.

We're pretty excited, so I cordially invite you all the give it a try and let us know what you think.

Sunday, March 13, 2011

Why Android Tablets Will Dominate

The Allegory of the 3 Series
The 3 Series is a magnificent car. It is not too big, not too small. It is safe, aesthetically pleasing, thoughtfully designed, expertly engineered and very well-built. It provides a thrilling driving experience and although it costs a bit more, both new and used models are still affordable for most folks. In many ways the 3 series is the perfect car and yet, not everyone drives a 3 Series. Even people who freely acknowledge its magnificence. Why?


Android Smartphones
2010 was a great year for Android phones. In the US, they outsold the iPhone and BlackBerry combined, saw 1600% growth in Europe and displaced Symbian as the world's #1 smartphone OS. All this in the same year that Apple released their best iPhone, whose lineage had an year-and-a-half head start on Android. The reason for this popularity is simple - unlike the iPhone which is a rigid, one-size-fit-all solution, Android phones come in a dizzying array of features, sizes, customizations and price points, allowing people to select the phone that's right just for them.


Android Tablets
Consider the leading-edge tablet OS contenders: Android, BlackBerry Playbook OS, iOS and webOS. Of those, only Android has been designed from the very start to be flexible and open enough to be adapted to different needs and uses. Within a year (or perhaps even this year's holiday season) we will start to see the same kind of diversity in Android tablets as in Android phones. Screens from 5" to 12", tablets that are thin glass slabs, tablets with sliding keyboards, laptop-like clamshells, dual-screens and god knows what else. The fact that the iPad has a big head start and many more applications in March of 2011 will prove as irrelevant in the long term as the iPhone's head start. Only Android will be able to provide consumers with a modern tablet OS in a device suited for their particular needs.


Different Strokes for Different Folks
I don't think this calls for pessimism on Apple, RIM or HP. I think they'll all continue to put out great products, maintain a sustainable market share and influence the direction of the market. However, I have little doubt that Android will be the way the majority of the world's people will interact with smartphones, tablets and other digital devices that'll dominate our interaction with technology in the coming years.

Thursday, February 10, 2011

The difference between Android and iPhone illustrated

I was a iPhone-only user for about 2 years when I got my Nexus One last year. Instead of ditching the iPhone, I've been using both devices for the past year - the Nexus One as my phone and internet device (email, browsing, etc) and the iPhone for music and gaming. I take both of them when I travel, when I go to work, when I get in the car, etc. After a bit, I realized I didn't want to ditch either of them, as I liked and disliked things about both of them, and thought of an interesting way of explaining that.


iPhone
The iPhone feels simple, yet complete. It knows what it can do, does it very well and rarely screws up - the homescreen is a simple icon grid, all settings are in one place and everything is smooth and neatly animated. The downside of course is, that is feels a little dumb - notifications are uselessly simplistic, apps can't tie into each other and worst of all, you have to use iTunes - the music player/content store/social network/central hub/software configuration system/kitchen sink monstrosity that makes me yearn for the days of Real Player.



Android
Android feels smarter and more ambitious, but very much incomplete. It allows you to personalize your device as much as you want, apps can tie into each other and adjust to different phones and it uses Google's cloud as an integral link to the device - your email and calendar just show up, apps can be pushed from a browser and software updates are quick, painless and delivered over the air. The downside is that Android is still very much a work in progress - you can wipe your device and sign into another and your email/calendar/contact list will show up, but not your call or SMS log. Music? Figure it out yourself!



Growth and Development

Both platforms are changing and the analogy applies here as well. We can imagine Android to be a big puzzle that Google solves in public by adding more pieces all the time, whereas we can imagine Apple releasing a complete, solved puzzle once a year - each puzzle being larger than the previous, yet still containing the previous year's puzzle in itself.
Ultimately both have to borrow a lot from each other's play book - Apple must eventually ditch iTunes as a hub and move to the cloud (image the absurdity of using your PC to sync your phone in 2015), while Google must still deliver important pieces like purchasing music and other content.

Thursday, March 18, 2010

The Nexus One as a halo product

Recent estimates of Nexus One sales have revealed that Google's very own smartphone has been selling at a far slower pace than many other smartphones, including the original iPhone, the Motorola Droid and even the BlackBerry Storm. In the ensuing online discussions, people speculated that the poor sales were due to Google's inexperience with retail sales, the novel phone distribution model and a variety of other plausible reasons.

Without knowing what Google's real expectations of the Nexus One are, I will speculate that big sales numbers aren't necessary for the Nexus One to be considered a success. In marketing, the halo effect is a term coined to explain how one product's positive traits translate into increased positive perception of the whole brand. Many companies produce such "halo products", especially in the automotive industry where virtually every car company spends a lot of time and money developing models which sell in tiny numbers. For example, Ford built just over 4000 Ford GTs over several years, while they sell over 2,000,000 cars per year.

While the Nexus One isn't (relatively speaking) as high end as the Ford GT, looking at it as a halo product makes it look fairly successful. Namely, it has brought of a lot of positive press and attention towards the Android platform, while acting as an excellent showcase of what the platform is capable of. This strategy also makes sense when you consider that Google relies heavily on their partners to sell devices. By positioning the Nexus One as a halo product, Google can generate a lot of positive brand awareness for Android and help their partners sell more units, while at the same time pushing their partners to keep up with the rapid evolution of the platform.

For a software company, it is a pretty good strategy.

Saturday, December 19, 2009

The iPhone 4G Predictions

Apple has introduced all three iPhone iterations during the summer, starting with the release of the original in 2007. Given the fast-moving nature of the industry, Apple will most certainly introduce a new iteration of the iPhone next year, if not during the now-typical summer season, then for sure before the holiday season of 2010.

Considering the iPhone's strengths and weaknesses, as well as the state of the competition, the following is a look at what the likely "4G" iPhone will look like. It is based not on sources, but extrapolation of current trends and an attempt at reading the market, so while these predictions are conservative, I also think they're fairly likely to come true.


Screen Upgrade
When it was introduced in 2007, the iPhone boasted one of the best screens on a mobile device, however it has not changed 2 and a half years while phones like the Motorola Droid or HTC HD2 have been introduced with larger, higher-res screens(3.7+-inch, 800+pixels). Apple clearly has to upgrade the iPhone's screen soon to remain competitive, however one of the iPhone's advantages has been providing a unified platforms for developers where all devices have the same screen.

Thus, I think its highly likely that the next iPhone will have a 960x640 screen impacting existing applications minimally by upscaling everything by 2. Developers will have to upgrade their image resources, but impact beyond this should be minimal. In addition, given the increased density, I think the screen will be bigger than the current 3.5". By cutting back on the large amount of dead black area on the face of the device, Apple should be able to fit in a 3.7-4" screen without noticeably altering the device's profile.


CPU and Memory
The 3GS gave us a much needed speed improvement, but the iPhone is still a very resource-constrained device, so while I think the CPU may see only a moderate speed increase (maybe 700Mhz compared to the current 600), I think the device's RAM will be doubled to 512MB.


Radio Quality
Given the high-end nature of the product, the call and connection quality of the current crop of iPhones can be described as "mediocre" at best. In positioning the iPhone as a gaming, internet and multimedia device, Apple has been able to get away with this so far, however I think the next iteration of the iPhone will have some noticeable improvements in its DSP, as this will improve one of the product's biggest weaknesses.


Camera
The current 3MP camera is pretty average and improving it seems like low-hanging fruit, so I think we'll see at least a flash and possibly a 5.2MP camera in the next iPhone.


Storage
I think the current 16GB and 32GB models are more than adequate for the vast majority of users, so I think its unlikely that we'll see a 64GB iPhone.


App Store Genius
With over 100,000 Apps in the Store, it's getting increasingly hard to find new apps. Using your list of installed apps (and possibly how much you use them) and your App Store ratings, it would be straightforward to build recommendation system for the App Store. Apple already has the genius feature working for music and with the Netflix Challenge winner's algorithm being publicly available, they also have access to a top-notch algorithm.


More Developer Power
While I am not very hopeful, perhaps the continued success of Android and its openness combined with continued developer complaints about its review process will convince Apple that is perfectly OK to give developers more power, such as access to system logs or background processing. Phonalyzr is one example of a somewhat popular Android app (currently #8 in the communication category) that is impossible to write on non-jailbroken iPhones.

Monday, November 30, 2009

Why Perl Lost It

Over the last several years it has become fairly obvious that Perl has lost the prominence and popularity it enjoyed in the late 90s and early 2000s, which can be seen from many different angles:
  • Google Trends [1] and the TIOBE index [2] show a steady decline over time [1]
  • A wide reaching survey at Langpop places Perl near the bottom [3]
  • A lot of Perl talk centers around people vigorously stating that Perl is not dead [4] and other kinds of cries for attention [5]
There are many reasons behind this decline, but put quite simply, Perl was outclassed by the competition and lost mindshare amongst developers.

On the low end, PHP became the defacto web development language thanks to its ease of development and deployment. While many developers decry PHP's ugliness and its simplistic nature (no closures, no namespaces, 3000 functions), it nevertheless made web development far more accessible to everyone and thus allowed a huge number of people to make the products they wanted, and helped some notable companies (Flickr, Facebook etc).

On the other end, Python's steady improvement over the years (which made it both more powerful and easier than Perl) attracted a lot of companies and developers, while Ruby and Rails attracted developers who wanted more flexibility out of their language. While this was happening, there were no significant releases to Perl5 and Perl6 was nowhere in sight.


Another significant factor I believe was Perl's much beloved "There's More Than One Way To Do It" principle. While marketed to developers and giving them freedom and flexibility, it also hamper's Perls practicality.

First, it makes the language extraordinarily complicated. While most good designs struggle and strive for simplicity and coherence (the K.I.S.S. principle), Perl goes for the kitchen-sink mentality. Its table of operators can only be described by "gargantuan" and is only eclipsed by its grammar, which is at least 5 times larger than the grammars of languages like Python and Haskell. What this means is that Perl demands far more time out of a developer to become proficient at it, while offering no significant benefits for someone investing this extra time.

Second, it makes it hard for the community as a whole to progress. For example, while Python added new-style classes and pushed everyone into adopting them, there is no way for Moose to easily obtain the same ubiquity (as no one can push it and enforce it). In fact, it is rather telling that Perl's premiere web development framework, Catalyst, only acquired a decent object system in mid 2009.

Whether Perl will continue to decline or not is hard to say, though I highly doubt it'll ever return to its former glory - neither Perl5 nor Perl6 seem to offer much for developers who do not already love Perl.


[1] http://www.google.com/trends?q=perl%2C+python%2C+ruby&ctab=0&geo=all&date=all&sort=0
[2] http://www.tiobe.com/index.php/content/paperinfo/tpci/index.html
[3] http://langpop.com/
[4] http://www.slideshare.net/Tim.Bunce/perl-myths-200802?src=embed
[5] http://blog.newint.org/tech/2009/11/26/perl-dont-ingore-it/
Easter Egg: The Forex Chart Monkey gives advice on Picket Prevention and Forex Technical Analysis

Saturday, November 21, 2009

The Making of BlockBattle.net

Welcome to the first of a series of blog posts I'll be writing about the ongoing development of BlockBattle.net. Although the project is several weeks old, it is still early in the development life of the game and I am hopeful that these posts will provide some insights to other developers about working with some interesting new technologies, as well as random tetris and network-programming related tid bits.


BlockBattle.net is in essence a modern implementation of the classic Tetrinet game. For those who are not familiar with Tetrinet, it is a fun and well-made multiplayer version of Tetris. Up to six players can join a game, then divide themselves into teams. Once the game starts, every player gets to control a single tetris field. When they make a line in their field, a random block will turn into a special power/attack and if a line is destroyed that includes that special power/attack, the power gets transfered to the player's attack queue. As the game progresses and players make lines and accumulate powers, they can use those powers/attacks either on themselves or on other players. For example, if a player gets a Clear Line and Add Line powers, they use use Clear on themselves and Add on an opponent.


While the original Tetrinet was great, it is now an old game (it was first released in 1997), works only desktop OSs and makes it really hard to find players on demand. BlockBattle.net (so named so that it does not infringe on any trademarks) will be web-based version, available across modern web-enabled devices (iPhone, Android etc) as well as any modern web browser. In addition, BlockBattle.net will offer automatic on-demand player matching and focus on simplicity of game play. It is my hope that BlockBattle will turn out to be a novel, fun and engaging game for users, while offering an interesting exercise in game, UI and web development for the developers.

The major design outlines of BlockBatte.net are:
  • The front-end game play will be done in JavaScript. Piece movement, generation, etc will be done client-side, while major events (dropping a piece, attacking an opponent) will be sent to the server so all player fields are synced at all times.
  • Using HTTP Long-polling (AKA Comet) to enable the sever to push events to the client, such as the player getting attacked.
  • Rather than the Tetrinet way of finding players, whereby one person starts a server and other players connect to the IP, BlockBattle.net will try to automatically match players, so users can simply log in and start playing
  • Making the game accessible on mobile devices by embedding a WebBrowser within an application, then making local inputs (buttons, gestures, taps etc) control the game.
Some of the technologies we'll be using:
  • JavaScript/DHTML for the game front-end.
  • Tornado Webserver - Tornado is a real-time python webserver that powered FriendFeed's website. Tornado was chosen because it is a fast, lightweight framework well suited to the needs of a push server. As well, it is written in Python which is popular, easy to develop for and quite powerful.
  • Mobile Apps: Popular mobile devices such as the iPhone, BlackBerry and Google Android phones will have native apps for BlockBattle, each of which will offer as simple UI customized to the handset and the kind of controls that are suitable for it.
----------
For some silliness, check out the Forex Chart Monkey that helps you with Pickpocket Prevention and Forex Technical Analysis.

Friday, May 22, 2009

Why the BlackBerry Storm 2's UI Could be a Winner

The original BlackBerry Storm came out in early December and despite a fair amount of anticipation and heavy promotion by RIM and its launch partners (Verizon in the US, Bell and Telus in Canada), the device received a thorough skewing in the blogotubes.

The complaints against it were numerous and ranged form well-deserved criticism to trollish whining, the most valid of which were:
  • A generally crummy build of the OS
  • The odd, love-it-or-hate-it-but-mostly-hate-it click screen.
Despite this, the Storm has sold relatively well - breaking the 1 million units sold about quicker than the original iPhone.[1]

However, it seems RIM is not satisfied with this and has taken people's complaints quite seriously. The unstable software (which was, at least somewhat understandably, rushed in order to catch the holiday season) has been undated to remove many of the original problems, however solving the hardware problem is much harder. Earlier today, Engadget posted some photos of the rumoured Storm 2 [2], which is due many months ahead of the usual 12-16 month refresh cycle, along with confirmation that the tacticle "SurePress" screen of the original Storm is gone.


In order to understand why the original click screen was needed we have note the differences between the BlackBerry OS and its main competitors - Android and iPhone OS. While both Android and the iPhone were under active development (2005-2008), the BlackBerry was already a pretty full-featured smartphone established in the corporate space. In order to support a multitude of features (the BB email app can do almost everything desktop Outlook can), the BB OS takes a more desktop-app like approach in which there is a distinct difference between selecting items and performing actions on the items. This makes much sense when supporting things like selecting several emails and choosing one of many different actions to support (moving to folders, deleting, flagging etc).

The iPhone OS and Android on the other hand, do not support selecting items and instead opt for a narrower feature set with a simpler UI. This works well for a lot of poeple, however the approach will breakdown if too many actions are supported. For example, forwarding and replying on the iPhone show up as buttons when an email is opened at the appropriate key is pressed, but what would the UI look like if instead of 3-4, there were 10-15 such buttons?


Being constrained by the way their OS worked, RIM thought they had a good solution in letting the touch screen do the selecting, while the pressing of the screen performed the action. Unfortunately, this turned out to be a huge bother in most use cases, such as selecting menu items, pressing buttons and especially typing. Thus, the SurePress screen turned out to be both essential and devilishly annoying.


With the Storm 2, RIM seemed to have realized this mistake and are touting something called the TruePress screen. While no one at the gadget blogs (Engadget, CrackBerry, Boy Genius, etc) seems to have use the Storm 2, I think that by making a few small changes, RIM could have a real winner on their hands. Namely:
  1. By removing the click screen and going with a touch-only screen, RIM can make the user experience much better in the vast majority of cases (selecting menu items, clicking buttons) by not requiring the odd screen-click
  2. In order to support the essential differentiation between selecting items and performing an action on an item, RIM could require that in cases were something could be selected (a list of emails for example), a single capacitative touch could select the item, while a double-click would perform the action. In addition to freeing them from the click screen, a double-click would also be familiar to a lot of people used to laptop touchpads.
If RIM gets the touch screen right the second time around, virtually all of people's complaints with the original Storm would be solved - it would have a gorgeous screen, intuitive touch interface, more solid build quality, more refined software all backed by the Blackberry's impressive featureset and system integration.

Whether the Storm 2 will be able to solve all the problems and preset a credible threat to Android and the iPhone remains to be seen.



  1. http://www.engadget.com/2009/01/27/verizon-touts-1-million-blackberry-storms-sold-to-date/
  2. http://www.engadget.com/2009/05/21/blackberry-storm-2-the-unofficial-hands-on/

Tuesday, December 30, 2008

Priced Android Applications Coming Within Weeks

I received an email from the Android Market earlier today containing some very pleasant and eagerly-awaited information. First, the Android Market will be expanding to many more countries in the coming weeks, with Germany, Austria, the Czech Republic and the Netherlands leading the way in early Q1 '09 followed by other European and Asian countries. These rollouts will no doubt coincide with T-Mobile's launch of the G1 in these countries and developers will have the ability to make versions of their app available only in those markets.

Second, and more important, Google confirmed that the Android Market will start supporting priced applications starting with the US and UK in early Q1, followed by Germany, Austria, the Netherlands, France, Italy and Spain as the local payment systems are set up. A lot of people have noted that the Android's Market is currently somewhat outclassed by Apple's App store, both in terms of the number and quality of the applications available. However, with the arrival of priced applications, and the profit motivator, we should finally see a competitive answer to Apple's App Store as developers start releasing apps they've been working on but were unable to easily sell.

Saturday, November 15, 2008

Phonalyzr is Out

After plenty of work and re-work I am extremely happy to announce that the first version of Phonalyzr went out on the Android Market today. Phonalyzr aims to provide analytics for your calling habits which are both interesting and useful, allowing you to see graphs, statistics and breakdowns which were either inaccessible or impossible before.

In keeping with the "release early, release often" philosophy of software development, the first version provides a basic, yet complete implementation of the final idea and really marks the beginning rather than the end of its development.

I want to thank everyone who has sent me encouraging emails and I look forward to releasing future versions that make the app more complete and useful to everyone.

If you would like to see some screenshots and get more info, please visit http://www.phonalyzr.com