VisorCentral.com (http://discussion.visorcentral.com/vcforum/index.php)
- Springboard Modules (http://discussion.visorcentral.com/vcforum/forumdisplay.php?forumid=10)
-- Springboard as a sort of "Docking Station" (http://discussion.visorcentral.com/vcforum/showthread.php?threadid=5001)

I think most of us have thought of springboards that are mostly smaller than the Visor itself. But what about springboard connections where you would actually attach the Visor to a larger piece of equipment? Therefore using the Visor as more of a "control" or something along those lines.

Imagine walking up to an ATM without a "screen" but rather a "springboard" connector sticking out. You plug in your Visor and whalla. It could ask your Visor for your account and pin number, ask you what you want to do (withdraw, check balance), and even update your accounting application data with balances etc.

What if you had a "springboard" connection in your car that told you gas mileage, travel mileage, or other "electronic" information that some cars use today.

"Springboard" connections could be used in many different ways, the possibilities are endless. Basically I'm talking about connecting the Visor to something instead of connecting something to the Visor...

Any thoughts? Cool ideas???

Though I don't disagree with the usefulness of what you're describing, I think it's expecting too much from this technology. Just the two applications you mention would demand both the automotive and banking industries accept the module concept (and Handspring's specifically) as a standard, and then work fast to implement it. Ain't gonna happen.

I think there are already enough 'standards' out for handling this type of service. For example, IrDA could provide a simpler interface (no hardware compatibility concerns), and Bluetooth will perform this type of messaging securely.

This is *exactly* how I envision Springboards to be used. In fact, it seems reasonable that many vertical-market devices would be bundled with the Visor as its sole controller. For instance, a maker of a GPS device can bundle the Visor with its device, so that they wouldn't have to re-engineer the input/display technology. Rather than licensing the PalmOS technology, they can instead license the Visor device.

But I agree with Zippy: I don't really think the automotive/banking industry would want to standarize on a specific company's technology. They'd probably rather use IR signals to transmit signals to devices (via TCP/IP or some other protocol). In fact, don't some ATM's in Europe already do this?

Those examples were a bit far fetched but the easiest ways for me to explain what I was trying to get across on a larger scale. This sort of "functionality" would take a long time for large industries to switch to and there would be many hurdles to get over in doing so, therefore I agree with what you're saying Zippy.

Hagop has my idea stated a little better in describing the Visor being reused for display and control purposes on various other devices. This would allow a "common" interface to devices that would give people a little less of a learning curve if it caught on...

Actually, I think a Bluetooth springboard module is much more likely. And I'd love to see a module to let Visors talk to iButtons. Anyone know how fast the serial port on a Visor can go?

One more post from the past..

I thought that this is an intresting Idea that hasn't been talked about much sence this. In your car it would work, but like for an ATM the bluetooth module under development would be a better choice. hmm love this old posts!

-miradu2000
Visorcentral past, present, and future