Why Google Choosing Arduino Matters
ptorrone writes "Earlier this week at Google I/O, Google announced the Android Open Accessory kit which uses the open source hardware platform, Arduino. MAKE magazine has an in-depth article about why Google choosing the Arduino matters, why Google picked Arduino and some predictions about what's next for Apple's 'Made for iPod' as well and what Microsoft/Nokia/Skype should do to keep up."
It already existed (an android-arduino "interface"). It only matters because google is behind it now (with an official API), but whoever wanted to do stuff before already could.
A friend recently made a "magnetic core memory" extension board for an Arduino:
http://www.corememoryshield.com/report.html
Just an example (with pictures) of what can be done with these things. (Magnetic core memory was the main form of non-volatile memory for computers from the 50s through to the 70s.)
Expert in software patents or patent law? Contribute to the ESP wiki!
Why are they charging nearly $400 for something that you can buy separately for $200?
Well, you can use the same chip (ATmega2560) for any commercial application, so you can use the Arduino for prototyping and then reuse the code for the final product.
Dilbert RSS feed
I see I did not get in before the Arduino haters. Yes, I know, it's a simple board, I understand that it's not a PIC or whatever embedded thing you prefer. I accept that. But it's a nice, easy to use board. It's fun. You can do stuff quickly with it. It's good for quick little things. I'm sorry that us Arduino users don't measure up to your expectations. I'm not going to tell you that you are wrong for your embedded choices. Can I get the same courtesy?
When It Counts.
Don't most Android phones have the bits needed to watch TV over the network connection built right in?
Nerd rage is the funniest rage.
Keep in mind that the *any* device that supports USB Host mode can be an Accessory. There's a full open source reference implementation for Arduino, but the protocols are documented and open and you can implement it on any hardware you like.
Docs and Specs: http://accessories.android.com/
Google IO Talk: http://www.youtube.com/watch?v=s7szcpXf2rE
Depends. It could be that the part will basically be used to repackage data so that a on-phone app can deal with it.
Consider their demonstrated use case of a exercise bike feeding activity data to a phone app that then use that as input for a game.
comment first, facts later. http://chem.tufts.edu/AnswersInScience/RelativityofWrong.htm
I'm not Bad Analogy Guy so I'll be a bit more literal: The point of Arduino is precisely that dumbed down programming environment, it brings the concept of basically making something computerised (to a point) to an a MUCH larger group of people than before. Right now there are tons of people out there doing things with these chips, making all kinds of little hacks and projects, that would ordinarily have thought "Hey what if I could do X? Oh, too complicated, what a damn shame" and are instead thinking "An arduino could probably do that".
Now for anyone that really does know coding and how to work chips and whatnot giving them an Arduino and making them use it "normally" is like giving them Duplos, but it's still Strictly Better for everyone to have these kinds of easily accessible solutions around for all the people that DON'T know that kind of thing. Sure a lot of them basically just sit there in easy-mode and never go any deeper but others will learn more in time, and just having it THERE makes the concept that much more ubiquitous.
A bullet may have your name on it but splash damage is addressed "To whom it may concern."
You just answered your own question, and you still don't understand?
"it comes with some dumbed down programming environment for people who don't want to use C/assembler."
Bingo!
How many people do you know that were taught assembler in school? I was taught because I was in an industrial electronics program, emphasis on industrial manufacturing and maintenance. I think they quit teaching assembler to CS students in the mid '80s, and quit teaching C soon after, shifting to C++/Java. How many people do you think were programming PCs when you had to flip switches, as compared to just typing it in and hitting enter?
CLUE: Make something convenient to use, and people will use it. Make it necessary, but inconvenient, and people won't. Are you sure you're smart enough to be allowed here?
When you want something built, come see me. If you want correct grammar and spelling, get a F*ing liberal arts student.
I agree 100%. Arduino is like the legos of microcontrollers. I've used many plain Atmel microcontrollers before and there was a steeper learning curve, whereas Arduino has been very quick, cheap and FUN!
There is also the benefit of reasonably standard IO wiring, so that when the community shares projects they are dealing with common hardware layouts.
1. This is obviously designed for those who make hardware as a hobby. It's a cool hobby, and every once in a while something that would be useful generally comes out of it, but makers aren't making stuff that the average person wants.
You know what caused the last couple of tech bubbles? The fact that it's really easy to write some software as a hobby, then commercialise it later. Google wants to do the same sort of thing with Android accessories. If 1,000 people make an accessory as a hobby, then one of them may have a really great design. They can then probably get funding to turn it into a shipping product (I imagine that Google has primed some VC funds to do exactly that). Going from working prototype to shipping product is largely a question of having sufficient money to invest.
I am TheRaven on Soylent News
Just posted here: http://groups.google.com/group/openmanufacturing/browse_thread/thread/8d32987e3767c868#
So, is this going to make an Android phone an important part of a lot of open source hardware projects (including RepRap perhaps)?
Note also: ..."
http://faircompanies.com/diy/view/make-your-own-open-source-android-smartphone/
"Flow DIY is an open source hardware platform so anyone can make a smartphone with the Android operating system and the exact capabilities one is looking for. Its components as well as the final creation by the user are open source, a first step toward the generalization of DIY devices. Interest is growing in personalizing not only software and web applications, but in everyday devices. A legion of DIYers are demanding tools to create increasingly more sophisticated devices.
As I've said elsewhere, with the turnover rate of Smartphones, in two or three years, today's generation of smartphones will be free-as-in-discarded. :-) So, it can make sense to build stuff for them, especially since if they are free-as-in-discarded-beer then they can be free for kids to use for educational things (like instead of the OLPC XO-1). Reference:
http://listcultures.org/pipermail/p2presearch_listcultures.org/2009-November/006250.html
That's one reason I started working on Android software (and under a three-years-and-its-free-under-the-GPL model that I am still conflicted
about).
http://www.artificialscarcity.com/
Still, sadly my Google Developer Smartphone died several after I got it and I never got around to sending it in for replacement, so I guess there is an amount of old phones that will not be usable for similar reasons (but I doubt that will be the majority). Also, as people have pointed out, the Smartphone batteries tend to go, making them less useful as they age (although I guess you could hack in some alternative power if you were motivated).
Still, I'd suggest that if one is making an open manufacturing project that requires computing, integrating an Android Smartphone might be an interesting idea.
A 21st century issue: the irony of technologies of abundance in the hands of those still thinking in terms of scarcity.