The Following 6 Users Say Thank You to ragnar For This Useful Post: | ||
![]() |
2008-11-03
, 09:17
|
|
Posts: 3,790 |
Thanked: 5,718 times |
Joined on Mar 2006
@ Vienna, Austria
|
#232
|
I appreciate your concern - even I wouldn't want functionality to be reduced and become something stripped down to a cell app variant in any way - with only a bigger screen to show for it.
But I think you are mixing 2 things here - UI design and functionality.
Making the UI simpler doesn't mean function will become simpler and reduced. The UI is a design element of usage - while function is what the application can do. UI is how you do it (on the screen).
So I don't see the two to mean the same thing. At least I am also like you - not wanting the function of the applications or platform becoming simpler and reduced - but I do want the UI becoming simpler - to make it easier to use on the tablet form factor - as a mobility factor.
![]() |
2008-11-03
, 10:19
|
Posts: 14 |
Thanked: 4 times |
Joined on Sep 2008
|
#233
|
![]() |
2008-11-03
, 10:30
|
|
Posts: 1,635 |
Thanked: 1,816 times |
Joined on Apr 2008
@ Manchester, England
|
#234
|
The Following User Says Thank You to lcuk For This Useful Post: | ||
![]() |
2008-11-03
, 11:55
|
Posts: 137 |
Thanked: 138 times |
Joined on Sep 2007
|
#235
|
1 there will not be a stylus with n900
2 the finger friendly ui is the main thrust
3 "fat scroll bars" will be gone, I personally see this as a pointer to a general canola style/pdf reader "arrows appearing" style
4 there will not be a d-pad
The Following User Says Thank You to chlettn For This Useful Post: | ||
![]() |
2008-11-03
, 12:27
|
|
Posts: 3,790 |
Thanked: 5,718 times |
Joined on Mar 2006
@ Vienna, Austria
|
#236
|
no stylus hopefully means a capacitive TS, otherwise it makes little sense.
![]() |
2008-11-03
, 12:36
|
Posts: 137 |
Thanked: 138 times |
Joined on Sep 2007
|
#237
|
Fingers on a capacitive touchscreen... What a great combination for selecting text for copypasting.
There's a reason why you can't do this on the jPhone.
![]() |
2008-11-03
, 13:06
|
|
Posts: 5,478 |
Thanked: 5,222 times |
Joined on Jan 2006
@ St. Petersburg, FL
|
#238
|
I'd be more than happy to live with a UI that I find a little clumsy if functionality isn't reduced. As I stated above in an answer to qgil: It's not that I'll find the perfekt device anywhere on the market. It's all about compromise. I already live with a half-hearted compromise on OS2008, and I probably could live with Maemo5 if it doesn't restrict me any further.
![]() |
2008-11-03
, 13:07
|
|
Posts: 3,397 |
Thanked: 1,212 times |
Joined on Jul 2008
@ Netherlands
|
#239
|
Well, it's not limited to stylus v. finger, as you may want to switch views for other reasons. This happens all the time and may also be desirable for reasons as yet unthought of. Instead of binding a hardware key to the functionality, the hardware key and its binding should be a part of the UI and then app should provide the functionality. In some apps (media player) you may want different view switch than in others (such as PIM).
i keep wanting to use the [menu] key for exactly that.
a great number of input dialogs would go well with a simple/intermediate/complex UI option, just cycle round them.
also there is the Code/Design/Run cycle that the on device IDE should have..
![]() |
2008-11-03
, 13:07
|
|
Posts: 1,635 |
Thanked: 1,816 times |
Joined on Apr 2008
@ Manchester, England
|
#240
|
First of all, there is nothing that cannot be done, given enough effort. However, I didn't try to talk just about the basic differences... Yes, you can do a system with a reasonable effort that shows different size icons and buttons for the UI for stylus and finger, but at least I'm not a fan of doing things halfway, I tried to talk about "optimal" UI's. Optimal UI's should not feel like compromises.
Information density is basically split in half for finger vs. stylus, meaning how many controls or UI elements you can put on the screen. If you have a plan how you could design a system-wide style that would automatically accommodate the UI's so that the amount of information and the amount, size and placement of the UI controls in any given view would work for both stylus and finger optimized formats, please let me know about it.
My full quote tried to be: "It is not possible as a system-wide issue to design UI's for all the applications that would be 'optimal' for both stylus and the finger at the same time, unless nearly doubling the design and implementation effort." (emphasis added).
Yes you can do it by doing the design and implementation twice, and yes there are some small parts which you don't need to design twice, hence the "nearly". But just trying to squeeze stuff, have the same design, same components and same thinking for each of the UI views, will not be optimal for both stylus and the finger. The stylus does permit to place "more stuff on screen", whereas for the finger minimizing UI clutter and therefore having a bit more hierarchy works better. (Of course it's not as simple as that, but...)
A finger optimal UI won't be stylus optimal UI and vice versa. At least platform-wise, since people are going through different applications, in and out, switching between them, doing different tasks, different views and windows, having some apps stylus-driven (hey, i need to take the stylus out) and others finger-driven (damn, i need to put it back in) will not create a satisfying user experience.
Also the example about advancing touch UI's further with things like multitouch (nothing announced, sorry
But also as noted in some of the comments here, nothing basically prevents "you" as the developers from doing otherwise.