I haven’t had the chance to do so in the last couple years, but this year I was finally able once again to help critique student work for Barry Kudrowitz’s Toy Product Design course at the University of Minnesota. It’s always great to see the interdisciplinary reach Barry’s work is achieving.
You often hear that to work with graphic displays on the Arduino platform you need to use a Mega or other high-performance board. I got curious about how much you can actually get done on an a measly Uno and similar boards based on the classic ATmega328P. You can find the ongoing results on my wiki.
With the mainstream shift away from desktop to mobile devices, it seems the relevance of open source ecosystems is diminishing. The two major mobile OSes have a very effective grip on the mobile OS space, and they have engendered app models that do little to encourage or motivate open source designers and developers. So now might be a good time to remind ourselves of some of the benefits that open source projects confer.
The benefit I am considering increasingly is the control open source projects give communities over their experience and priorities. In particular, in the current mainstream device use context there’s little room for economically disadvantaged voices. Where the entire raison d’être of a platform is monetization (something that applies to both mainstream mobile platforms, though they go about it differently), lack of economic might translates directly to lack of impact.
The marginalization of limited income impacts everything from design (developing world personas aren’t likely to appear on a design team’s list) to implementation (everyone has a recent, fast device, right?). Open source projects empower communities to develop solutions tailored to their own needs, independent of their monetization potential or other considerations. So, no matter your role in society, if you want help establish more equity in the world, then please support open source!
In spite of some valiant efforts, a mainstream mobile OS that is truly open for users will not become a reality anytime soon. The next best thing we can do is focus attention on open source apps. In future posts, I will try to discuss some mobile open source projects that work well enough to replace popular proprietary and/or monetized ones. But for now, if you are on Android you can check out F-droid: the go-to store for open source mobile apps. Many of these projects are eager for contributions from designers and developers. But even your simple act of using an open source app helps to establish and promote it.
A recent chassis redesign project I undertook for Audio by Van Alstine is now in production.
This project pushed “constraints as creative resource” to the limit. The client specified that the design language and elements from the product’s predecessor be maintained—down to the knobs, faceplate treatments, and typography.
The project brief revolved around electronic and industrial design work to bring the client’s preamplifer platform up to functional parity with current market offerings within a framework that fits with the client’s existing manufacturing capabilities. The result is a platform that is significantly more capable than what it replaces yet easier for the client to manufacture. It is also amenable to comprehensive appearance changes if and when the client deems the timing is right.
So while it might not seem there’s much innovation on the outside, there is a lot of innovation for the client on the inside.
According to Fast Company, John Madea is positing that writing skills are important for design because many interactions still depend on text. I’d like to approach this from a different angle. What I’ve found in my personal development is that the better command I develop over my natural languages, the better everything becomes. Visual thinking, musical thinking, engineering thinking … everything.
I’ve heard some people describe my approach to design as linguistic. I also think of coding primarily as an extension of linguistic skills. So it might just be me. But since language is such a core part of how the human mind works, it could very well be universal.
So, yeah, writing.
Part One (in phase one) of Programming Fundamentals with Processing is 99.3% finished. Calling it done!
Kind of a big day here. I’ve decided to put online what I’ve written so far of my book on Processing. I’m pretty sure this will motivate me to do more work on it.
I’m about 80% done with the first half. I’m sort of thinking that once the first half is actually done, I might try a Kickstarter or GoFundMe.
Feel free to kick my butt about this.
There’s a growing series of good videos covering ESP8266 Tips & Tricks on ACROBOTIC’s YouTube channel. The ESP8266 has become quite a darling in the IoT world, and a seriously cool community is growing around it.
NodeMCU devkit picture by Vowstar (Own work) [CC BY-SA 4.0 (http://creativecommons.org/licenses/by-sa/4.0)], via Wikimedia Commons.
I am cautiously optimistic about the recently announced resolution of conflict between Arduino LLC and Arduino Srl. Back when the issue flared up, I took sides based on the information I had available, but I then decided to refrain from public comment as additional information on the issue did not seem to be forthcoming.
While I am hoping this announcement means a lovebath for everyone, I am concerned about some of the wording used in the announcement, specifically that, “The newly created ‘Arduino Holding’ will become the single point of contact for the wholesale distribution of all current and future products, and will continue to bring tremendous innovations to the market.” Does this mean that Arduino will shift its focus toward for-profit and more closed designs? In other words, will the hardware arm of the project maintain the project’s fully open culture? There have been signs that things have been closing up on the software side as well since Arduino LLC seem to be be in no hurry to answer questions regarding whether the code for their new SaaS IDE will be open sourced or not.
So, cautiously optimistic I am.
Since I had to install Arduino support in a new Netbeans installation, I decided it was a good time to document what’s needed. Check it on the wiki.