Two different sets GUI... one for weekdays, another for weekend, for example. Different shortcuts on the "desktops", widgets, theme... and switching between them back and forth.
By the way, I Loooooooooove my phone. Screw Apple.
-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Andriod UI - what are they thinking?
- Thread starter UIexpert
- Start date
- Status
Two different sets GUI... one for weekdays, another for weekend, for example. Different shortcuts on the "desktops", widgets, theme... and switching between them back and forth.
By the way, I Loooooooooove my phone. Screw Apple.
marefin
Android Enthusiast
-__- ........................... i think you're being EXTREMELY nit picky
at least we can agree on something
edit. i think i might have misunderstood what you were describing as "spaces" but the posts below made it a bit more clear. but still.........
OK - that was me that said that.
In the HTC Sense launcher, you get 7 desktop screens for each "scene" (but yes, it's better described as a "space" I'd suppose).
I was describing the seven part of the scene/space I've set up called "The Grind" - it's my everyday thing.
I also have a scene set up called "FUBozo" (I guess it has something to do with filling up clowns
) and it has 5 screens of just fun and no work whatsoever.I also have a scene set up called "Bay Area" and that one's 7 screens of totally work-related stuff.
I also have one called "Research" and another where I experiment called "Sandbox" - for obvious reasons.
Wallpaper, layout, very different in each case.
These scene/spaces don't see each other, don't collide, and I can switch between them with 3 taps total.
Somebuddy with ADW or LauncherPro experience can advise you if you can get similar behavior with those add-on launcher products. I've not used them, so I cannot say.
Here's where I have to disagree with you. When you say "should" and "only logical" implies that there is a universal and (if I may borrow an overused word from the Apple camp) intuitive modality for app behavior. What you mean is that it would be convenient based on the way you'd prefer Android to operate.
I do agree that in certain instances there is an overabundance of back-button pressing, but i would be equally annoyed if to get to a certain menu level or app screen I had to go forward several times because the app home button you suggest reset the apps state to just-opened (aka app home).
This is a big deal for you. I get that. It's a minor inconvenience to me when and if it happens. Honestly, until you even brought up the subject I hadn't considered the possibility.
Put it out there to Google and the developers that this is a desired feature. As long as it had no impact on the apps performance I'd support it.
Well - that's your opinion, but that plan fails when you're in the second screen someday, go 4 levels deep in a sub-hierarchy, and want that option to home you to the second screen instead of back to home of app.
(edit - Late again - exactly what lunatic59 just said.
)Take my suggestion that you suggest to Google a standard upper-right X button for hierarchical sub-menus to heart.
Web paradigms don't apply to Android.
They do however (you're gonna love this) apply to the other operating system that Google's been working on called Chrome - where the entire OS follows web browsing paradigms because the entire OS is a browser.
The heads at Google are good for much more than for holding up hats.
Agree with your post, and I'm asking what you think of the idea of a window-X for sub-menu popups.
Yes, you can with both. I've got ADW on my Nexus and LP over TouchWiz on the Captivate.
One of the other things you can do is install multiple launchers including the manufacturers UI (like Sense or TouchWiz) and then use something like Home Switcher - Android app on AppBrain to set up actual profiles in each launcher. The caveat is that if you use LP, you lose access to the Sense widgets and vice versa.
For me it's a non-starter, but I'd support the idea if there was no negative impact to performance. I don't know why there would be, but stranger things have happened.
I'd not noticed this before in my uses, so it's a non-starter to me as well - but - I can see his point and wanted to see if you'd thought of something immediately wrong with my suggestion.
I'd have withdrawn it if so.
Thanks for the info on launchers - I was never clear on their differentiation before!
adi19956
Android Expert
does Firefox work for you? I tried it and it doesn't work at all
No, no - not yet, I was waiting for a stable release.
Their web site says they've gotten there (hey - I been busy) now and it's Evo 4G tested - I'll have to give it another try.
List of supported phones - Firefox Mobile System Requirements
When it says "any Android 2.x and above" then it'll be ready for prime-time.
EDIT - Yes, I just gave it another test spin.
Not ready for prime time at all - yet.
IOWA
Mr. Logic Pants
They'd be tears of joy.
Srsly tho, I have to live with both, and you get used to changing gears.
Sammy's got it backwards.
Agreed
My wife and I have had a Droid Incredible each for a couple of months now. While mine is heavily customized and has changed at least once every week, hers is pretty much the stock system except for a spreadsheet app and a better calendar app on the home screen. I'm flirting with LauncherPro but I can't see much benefit over Sense.
What Android really needs is a quick tutorial installed as default on the phone. It took me a while to work out how the long press system worked within apps. We both accidentally dialled people several times when trying to edit their details in the phone book.
I'm trying to work out where the "home" screen would be for most apps. For an analogy, where's the home screen for MS Word or Excel? or for Outlook? "home" screen is pretty much meaningless for apps IMO, but makes far more sense for websites. The biggest issue with phones is that the screen space is too small to have a full menu ever-present like you can on websites and PC-based programs, so multiple presses are going to be a given for any kind of navigation. But of course, some apps are just badly designed.
What Android really needs is a quick tutorial installed as default on the phone. It took me a while to work out how the long press system worked within apps. We both accidentally dialled people several times when trying to edit their details in the phone book.
I'm trying to work out where the "home" screen would be for most apps. For an analogy, where's the home screen for MS Word or Excel? or for Outlook? "home" screen is pretty much meaningless for apps IMO, but makes far more sense for websites. The biggest issue with phones is that the screen space is too small to have a full menu ever-present like you can on websites and PC-based programs, so multiple presses are going to be a given for any kind of navigation. But of course, some apps are just badly designed.
Are you on the grid?
I FIGHT FOR THE USER!!!!
That just reminded me of Tron Legacy
Anyways...
There is no one right answer to the UI. It's not like a multiple choice questions where you either get the right answer or you don't.
I believe that the Android UI isn't the most intuitive. You go menu diving a few too many times and sometimes things can be a bit confusing in the beginning. But it's not like it like a old-school command line program where ^X is the back button or something ridiculous like that. But it works and enough people are using it so that says something.
Just use what works for you and be happy.
That was ^H by the way for backspace.
http://web.cecs.pdx.edu/~rootd/catdoc/guide/TheGuide_38.html
I still work this way.
http://web.cecs.pdx.edu/~rootd/catdoc/guide/TheGuide_38.html
I still work this way.
Essex
Android Enthusiast
This has been an absolutely fascinating thread to read. I'm a little late to the party but I have a few comments about Android's UI. At first I thought UIexpert was trolling (there was a poster on Engadget named uiexpert who trolled vigorously), but he made some points that I begrudgingly agree with. Most of us are experienced Android users who have become acclimated to the OS's quirks and limitations. Sure you eventually learn Android, but there is a learning curve. Perhaps Google could make the UI a little more standard throughout the various system applications. Perhaps the manufacturers recognized this and decided (with varying degrees of success) to supply missing features through proprietary software (Sense, MotoBlur, TouchWiz, etc).
I've been using HTC's version of Android (Sense) for over a year, starting with the Sprint Hero and currently on the EVO, and I like it. I recently purchased my sister a Nexus S, and it was my first exposure to stock Android. It was pretty jarring. While stock Android felt noticeably zipper than Android + Sense, I thought stock Android was so ... spartan. It lacks features that even my Hero had (namely power control widgets, and other shortcuts). For example, on my EVO, if I want to enable/disable my mobile network I just tap the "Mobile" widget on my homescreen. I couldn't find a similar solution on the Nexus S. To do something as simple as enabling the mobile network on the Nexus S, I had to wade through layers of the settings menu. My sis figured it out after I showed her, but she probably wouldn't have figured it out on her own. And she shouldn't have to. I don't think customs skins are going anywhere anytime soon as long as the underlying UI remains so sparse. Maybe stock will grow on me, but not until Google adds more built-in widgets, options and shortcuts...
Also, no Android phones come with file managers (AndroZip, Astro, et. al.) built into the UI. I think future iterations of Android should have a stock file manager. Android should also explain the file folder structure, either through a tutorial or an instruction manual. I had no clue that I could manipulate my files without plugging my phone into a computer, until I stumbled across AndroZip in the Market.
I think this is an important, informative thread. I've learned alot, and I've enjoyed reading all of the back and forth. Often, real growth comes from critical self analysis. I think we Android users shouldn't be afraid to criticize the OS, when criticism is warranted. I love Android but it could be a bit more accessible and easier to understand for the non-techie.
I've been using HTC's version of Android (Sense) for over a year, starting with the Sprint Hero and currently on the EVO, and I like it. I recently purchased my sister a Nexus S, and it was my first exposure to stock Android. It was pretty jarring. While stock Android felt noticeably zipper than Android + Sense, I thought stock Android was so ... spartan. It lacks features that even my Hero had (namely power control widgets, and other shortcuts). For example, on my EVO, if I want to enable/disable my mobile network I just tap the "Mobile" widget on my homescreen. I couldn't find a similar solution on the Nexus S. To do something as simple as enabling the mobile network on the Nexus S, I had to wade through layers of the settings menu. My sis figured it out after I showed her, but she probably wouldn't have figured it out on her own. And she shouldn't have to. I don't think customs skins are going anywhere anytime soon as long as the underlying UI remains so sparse. Maybe stock will grow on me, but not until Google adds more built-in widgets, options and shortcuts...
Also, no Android phones come with file managers (AndroZip, Astro, et. al.) built into the UI. I think future iterations of Android should have a stock file manager. Android should also explain the file folder structure, either through a tutorial or an instruction manual. I had no clue that I could manipulate my files without plugging my phone into a computer, until I stumbled across AndroZip in the Market.
I think this is an important, informative thread. I've learned alot, and I've enjoyed reading all of the back and forth. Often, real growth comes from critical self analysis. I think we Android users shouldn't be afraid to criticize the OS, when criticism is warranted. I love Android but it could be a bit more accessible and easier to understand for the non-techie.
If the Nexus S is widget poor, then maybe check out appbrain.com and do a search for curvefish
Don't know if they're Gingerbread-ready - but they're free and easy to try out.
Don't know if they're Gingerbread-ready - but they're free and easy to try out.
Essex
Android Enthusiast
Thanks to this thread, I'm gonna recommend "Beautiful Widgets" to my sis next time I see her. I checked it out last night and I think it's just what my sis needs on her Nexus S
Yes, that's exactly what I felt. Now after a week I don't feel it anymore because I'm used to it, but at first it felt so naked and raw... I'm still spending a couple of hours every day adding features and shortcuts.
P.S - file manager? Really?? Cool... I will have to check it
An update for Nexus S - includes a maps update - could clear up that 4 vs. 5 tap discrepancy.
Nexus S gets its first update over the air -- Engadget
Nexus S gets its first update over the air -- Engadget
Haha.. yes I did this update a few hours ago... I don't see any change.
The dialer is a good example for bad ui. You type a number.... now I want to make out of this number a new contact. You would imagine it would be right there, some icon or whatever... so you start searching for it but it's not there. You click contacts... nothing. So you click menu. You see "add to contacts". (before you type a number "menu" doesn't do anything) You click on it... now it says "add new contact" so you need ANOTHER click... Adding a new contact for a phone number would be the most important function, in my opinion (it's still primary a phone, right?) so how come the dialer is such a mess?
When I click on the dialer, why does it show me the call log? Why not the last screen I was on or, at the minimum, the contacts tab?
And I would include the search bar at the contacts tab by default... why do I need to click "search" (another click..........) instead of starting to type the first letters of a contact and jumping right to it?
So if I want to call someone, it looks like this:
Dialer -> contacts -> search button -> type.... find contact.
instead of:
Dialer -> you are ON contact with search bar ALREADY OPEN so you can start typing the name.
as I said.... no UI.
The dialer is a good example for bad ui. You type a number.... now I want to make out of this number a new contact. You would imagine it would be right there, some icon or whatever... so you start searching for it but it's not there. You click contacts... nothing. So you click menu. You see "add to contacts". (before you type a number "menu" doesn't do anything) You click on it... now it says "add new contact" so you need ANOTHER click... Adding a new contact for a phone number would be the most important function, in my opinion (it's still primary a phone, right?) so how come the dialer is such a mess?
When I click on the dialer, why does it show me the call log? Why not the last screen I was on or, at the minimum, the contacts tab?
And I would include the search bar at the contacts tab by default... why do I need to click "search" (another click..........) instead of starting to type the first letters of a contact and jumping right to it?
So if I want to call someone, it looks like this:
Dialer -> contacts -> search button -> type.... find contact.
instead of:
Dialer -> you are ON contact with search bar ALREADY OPEN so you can start typing the name.
as I said.... no UI.
There are lots of dialers, and many contain the exact behavior and features you're asking for. And for managing contacts, and quick calling you want Gesture Search, free in the Market.
I think since everyone likes to call them dialers, this is pertinent -
Rotary Dialer - Android app on AppBrain
I think since everyone likes to call them dialers, this is pertinent -
Rotary Dialer - Android app on AppBrain
B
Bnice
Guest
Maybe he needs to try another android device.(just saying)
Again - we are not using the same dialer.
Try that appbrain link, then search for dialer - you may be surprised at the options and layouts available.
And maybe I linked the wrong rotary dialer - mine, you have to actually dial, and it includes the racheting sound
Try that appbrain link, then search for dialer - you may be surprised at the options and layouts available.
And maybe I linked the wrong rotary dialer - mine, you have to actually dial, and it includes the racheting sound
- Status