Skip to main content

Power Pads, Cut My Loose Ends!

The idea has been floating around before, but finally seems to be coming into the light with efficiency and cost. The day will come soon when we can drop any of wireless devices onto a table and let them charge. When our desks will run power to everything sitting on them, without any connections or wires. Awesome.

They do say it could be many years before we get anything reaching wide support. The problem is that the devices need to support these new sources of power, and the devices won't support them until everyone has the new sources of power. You know how those great cyclic dependencies go. Now, we'll probably see them first in devices that are high end enough to warrant including stand alone power pads with them. I'll peg Apple's iPod as an early adopter.

However, I do have an idea to push these power pads more quickly: receives compatible with standard batteries. AA, AAA, and C are the most common batteries used today, so packing a receiver coil into the right shape unit would be just the ticket. That means any device taking a standard battery is automatically compatible with super convenient charging. The second step is for large deployments of non-standard batteries to migrate into receiver coils, allowing lots of existing devices like laptops and cellphones to suddenly gain the ability to charge wirelessly. As a bonus, putting the receiver coils in the batteries themselves allows you to toss extra batteries onto the surfaces for pre-charging.


Comments

Unknown said…
That's a great idea, assuming form factors get small enough, early enough in the adoption schedule. FWIW, there was an article in The Economist about this, so I guess it's "big news" now.

The worry I have is safety -- although this is inductive coupling, and thus very short-range, I'm not sure I'd like to store my hands and arms mere inches above it for the 10-12h/day I spend at my desk. At least not without understanding the health implications pretty well first.

Popular posts from this blog

CARDIAC: The Cardboard Computer

I am just so excited about this. CARDIAC. The Cardboard Computer. How cool is that? This piece of history is amazing and better than that: it is extremely accessible. This fantastic design was built in 1969 by David Hagelbarger at Bell Labs to explain what computers were to those who would otherwise have no exposure to them. Miraculously, the CARDIAC (CARDboard Interactive Aid to Computation) was able to actually function as a slow and rudimentary computer.  One of the most fascinating aspects of this gem is that at the time of its publication the scope it was able to demonstrate was actually useful in explaining what a computer was. Could you imagine trying to explain computers today with anything close to the CARDIAC? It had 100 memory locations and only ten instructions. The memory held signed 3-digit numbers (-999 through 999) and instructions could be encoded such that the first digit was the instruction and the second two digits were the address of memory to operat...

Announcing Feet, a Python Runner

I've been working on a problem that's bugged me for about as long as I've used Python and I want to announce my stab at a solution, finally! I've been working on the problem of "How do i get this little thing I made to my friend so they can try it out?" Python is great. Python is especially a great language to get started in, when you don't know a lot about software development, and probably don't even know a lot about computers in general. Yes, Python has a lot of options for tackling some of these distribution problems for games and apps. Py2EXE was an early option, PyInstaller is very popular now, and PyOxide is an interesting recent entry. These can be great options, but they didn't fit the kind of use case and experience that made sense to me. I'd never really been about to put my finger on it, until earlier this year: Python needs LÖVE . LÖVE, also known as "Love 2D", is a game engine that makes it super easy to build ...

My Software Job Transition Strategies?

I’ve been spending a good deal of the last two days preparing mentally for starting a whole new challenge as a developer. New things aren’t new to me, but this is different and big enough really call for some Deep Thoughts ™. For one thing, I’ve made a big move from the world of Python web development to totally other Python work and while web development has never been the only thing I do, it has been the only work that paid the bills. That transition isn’t one that bothers me or daunts me, though. Instead, I’m thinking about transitioning to the scope of the work I’m getting into. For a long time, I juggled multiple clients and client projects every day, so no single project usually took up most of my time. Every developer juggles time through the day, but exactly how that works in each company and on each project varies a lot. I was looking for a place that I could really focus in a way that I haven’t for a long time. I think I found that, but now I have to deal with the consequen...