One of the most compelling use-cases for tablets is the UI. I've been using computers for over 20 years and there are some interactions that are gesture based that are faster and more intuitive than traditional keyboard and mouse interaction. One basic example is e-book reading: a swipe gesture to flip the page maintains the familiar page paradigm, whereas clicking and dragging a scroll bar on a desktop is not burdensome, but less efficient.
While the computational power of a tablet is definitely lower than a workstation, the portability of a tablet would outweigh a musician's studio workstation. Given that Honeycomb 3.0 tablets are dual-core or better (I am assuming that quad core's like nVidia's Kal El will be incorporated), and that most will feature a GPU, it is like that OpenCL style optimizations can be made, which will be useful with DSP (which I would assume would be valuable to most musician-oriented apps). With the tablet as an adjunct as opposed to a replacement, I can see where a lightweight device could be used in a jam session and then synchronize back to your desktop app...so you've effectively increased your market. - Scott On 11-02-21 1:19 PM, "Mark Murphy" <[email protected]> wrote: >On Mon, Feb 21, 2011 at 1:06 PM, niko20 <[email protected]> wrote: >> I write audio apps for Android, and I was thinking about new features >> I could add to my apps to make them more powerful for use in "live >> play", etc. But then I realized something: What is the point of it? I >> mean, if a musician wanted to have a portable device with some nice >> software that they could use live on stage, wouldn't they just be >> better off getting a tablet PC or a small notebook? > >http://www.wired.com/underwire/2010/05/ipad-dj-rana-sobhany/ > >> I'm just not seeing a good reason to develop a "deep" functional app >> for use on an android tablet when I'm wondering if it's really >> "duplicating" software that would be better run from a PC. A PC that >> would no doubt have much more power than the tablet ever would and >> could give better features in the software anyway. > >Your audience will be tablet owners who would rather use their tablet >for your app than would want to use a desktop or notebook PC for a >substitute app. It is impossible to say in the abstract how big that >market is today or will be tomorrow for any given app. It is also >quite likely that their decision of going with the tablet vs. the >notebook will be made for other reasons; the existence of your app >simply eliminates one barrier to them making that choice. > >Also, bear in mind cross-segment promotional benefits. The tablet app >may not sell like hotcakes. But, if you can get good publicity out of >it (first to market, etc.), the tablet app may help drive sales of the >phone app. > >-- >Mark Murphy (a Commons Guy) >http://commonsware.com | http://github.com/commonsguy >http://commonsware.com/blog | http://twitter.com/commonsguy > >Android Training in London: http://bit.ly/smand1 and http://bit.ly/smand2 > >-- >You received this message because you are subscribed to the Google Groups >"Android Discuss" group. >To post to this group, send email to [email protected]. >To unsubscribe from this group, send email to >[email protected]. >For more options, visit this group at >http://groups.google.com/group/android-discuss?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Android Discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/android-discuss?hl=en.
