iPhone Gets New Groove Boxes: Is it Live Synthesis, or is it Canned?
The iPhone has become an almost absurdly-popular platform for music apps this year, even given more capable, more plentiful PCs. But to those who don’t yet “get” the appeal, talk to a mobile music addict: having the ability to be creatively musically in corners of time that would otherwise go unused, like a cramped bus ride, can be a beautiful thing. (Now, you start talking about taking away my PC/Mac experience, and I will start screaming in agony – but that’s a topic for a separate post.) The question is, what form should that app take? Today, I’ve got an iPhone round-up going as I clear out my news inbox, but that thread lies beneath all the stories…
I’m working on putting together a collection of truly productive, non-gimmicky/non-toy music apps now that the platform is maturing. But two apps released this week I think deserve special mention, and mention together – partly because of the different angle they take.
They’re both essentially handheld grooveboxes. They’re both relatively powerful, bringing desktop-style production to the platform. They’re both good options, and at this price, you might go buy both. But as I go off to test these two apps, I’m already struck by the contrast between the two.
One is the kind of app that we’re seeing a whole lot of on the iPhone, just as we once saw it in me-too apps on desktop computers. It assumes that the way to reach more people is to give them a whole bunch of canned loops that already sound like the styles they might want to play, and assume they’ll be pretty limited in their ability to do much with those loops.
The other of the two apps eschews the obligatory audio loops for real synthesis, and strips out the usual “let’s try to look like hardware” interface for something a lot more minimal and (I think) touch device friendly. That’s a design lesson that might well be applied beyond the iPhone, too.
/* Buy links if custom fields not null and not in cat or search results */ ?> /* End Buy links if custom fields not null and not in cat or search results */ ?>









