Related
ive trolled all over the forums and downloaded every cooked rom and 3rd party app or mod but i just cannot find a simple solution to what should be a very common and simple to fix problem.
So on the Touch HD there's 4 hard buttons along the bottom. From left to right let's refer to them as;
[1] Green (call)
[2] Home
[3] Back (left)
[4] Red (hangup)
I just want to hard-assign an action to [3] (the Back button) so when i hold it the active app closes. It's impractical to keep many apps open at once on these devices and baffling that the default behavior for most apps is to stay open and make the user click the tiny 'x' in the top-right to close them. Dumb. So far I've tried;
MobileMagic - doesn't have an action to 'close the active app' (have requested in the thread).
AEBPlus - click works but hold doesn't, so you lose the default 'back' function of the single press (not a bug, seems a limitation).
Custom app using .NET - I even wrote an app in .NET which uses low-level keyboard hooks and I can catch the press event but not stop it being forwaded which defeats the purpose.
GODDAMMMM is it that fkn hard!!!??? Can anyone help me out at all? I'm happy to code something up in .NET if anyone knows it can actually be achieved and ill post it up here.
Many thanks.
...oh and im talking about on WM6.5 by the way
Just tolled again through forums and toyed with dredsensor - also no good wont run on hd/6.5
Does it need to be the hold function of the button? Can't you just use double tap with AE Button Plus? Double (and even triple) tap work fine with my HD and AE Button Plus!
fair point....that could work...but i find sometimes the double-tap gets handled like a single tap which is why the hold is a better solution, but thats just my experience.
noofny said:
fair point....that could work...but i find sometimes the double-tap gets handled like a single tap which is why the hold is a better solution, but thats just my experience.
Click to expand...
Click to collapse
Yeah, I sometimes encounter that problem as well... But very rarely and only if my HD us running 10 apps at the same time and has therefore become very sluggish.
After reading an article from WMPU, about the back button and task switcher, i did some cut and paste job, and this is what i've made...
A lot of ppl complaint that the right black bar(the one with an arrow icon) is wasting a lot of space. The first apps' jumplist will use this space.
(1st attachment)
Another apps' jumplist, was to bring the notification bar even further. In WP7, user have to tab on the top black bar to get some information about the battery and the signal strength. The jumplist(which holding recent apps), drop together with the battery or whatever indicators.
(2nd attachment)
perhaps it looks nicer in this form:
(3rd attachment)
however, i think this will "crash" the "in call notification" or what ever it called...
What do you think? do you think such jumplist is necessary?
What I wouldn't mind seeing is basically a list sorta like the existing list when you swipe left on the home screen that pops up when you double tap the back button. Each would have a X that you could tap to nuke the app entirely or you could tap on the icon/name of the app and jump to it.
RustyGrom said:
What I wouldn't mind seeing is basically a list sorta like the existing list when you swipe left on the home screen that pops up when you double tap the back button. Each would have a X that you could tap to nuke the app entirely or you could tap on the icon/name of the app and jump to it.
Click to expand...
Click to collapse
I'd have to agree - my thoughts exactly Rusty!
When you said app jumplist I thought you meant a list like the contacts list but for apps. I thought the app list would get the same functionality as the other lists, but I haven't seen that to date.
why you need a "X" while these "recent" apps are not consuming your processor?
imhong said:
why you need a "X" while these "recent" apps are not consuming your processor?
Click to expand...
Click to collapse
To take them off the list, so it doesn't become cluttered, if you want to actively manage it.
RustyGrom said:
What I wouldn't mind seeing is basically a list sorta like the existing list when you swipe left on the home screen that pops up when you double tap the back button. Each would have a X that you could tap to nuke the app entirely or you could tap on the icon/name of the app and jump to it.
Click to expand...
Click to collapse
Not double-tap... hold. I want 2 taps to take me back twice.
On that note I think Voice should have been mapped to holding the Search button, not the Start button. There are better uses for the Start button.
I agree with the hold back button thing.
but task/app managers are flawed slighty if you have forgot and closed or not even opened that process yet.And its then another button to your start screen to open it again.I think a long hold takes you back to the start screen and the list shows like in picture one.best of both worlds.plus you could have a nice little animation of the list sliding in from the bottom like a train.
looks pretty neat. although if those icons were a tiny bit smaller you could line up 3 of the icons with one of the big icons. you have to have stuff lined up of else people like me will go mad
I personally love this idea.
I've been realizing lately how amazing android really is and customizable it is with this phone. Off topic but I kinda hated the fact. Of a recent app button and the fact that I lost the menu button (honestly the most used button on all my other phones). The devs here realized it and gave me the ability to have my menu button, get my search button back, and make recent apps come up by holding the home button. Got to love them. Shout out to our fantastic devs.
Now the point of this thread was just I wanted to know how you guys thought about a gesture bar instead of having buttons. So swipe on the bar to go back, maybe swipe up to go home etc? Just trying to think of creative ideas on how to use this huge screen and since everything is virtual, why can't this be possible. What you guys think?
Sent from my Galaxy Nexus using Tapatalk
nice idea, kind of like the microsoft touch mouse. I would like to see someone make that possible and see how it works out.
Shaquiel Harris said:
Now the point of this thread was just I wanted to know how you guys thought about a gesture bar instead of having buttons. So swipe on the bar to go back, maybe swipe up to go home etc? Just trying to think of creative ideas on how to use this huge screen and since everything is virtual, why can't this be possible. What you guys think?
Click to expand...
Click to collapse
As a technical exercise it sounds like a very good idea, but I know for one I wouldn't use it. Dolphin HD has had gesture support for such a long time and I used it as my main web browser on my Desire but I didn't ever use the gesture support.
Even my HD2 running WM 6.5.x had an app that allowed you to launch any app/program by configuring a gesture, but again I didn't use it.
I guess it's just easier to place my thumb than to move about when holding the phone in one hand. Is this an idea you were thinking of implementing yourself, or are you looking for someone to pick the idea up and run with it?
Kalavere said:
As a technical exercise it sounds like a very good idea, but I know for one I wouldn't use it. Dolphin HD has had gesture support for such a long time and I used it as my main web browser on my Desire but I didn't ever use the gesture support.
Even my HD2 running WM 6.5.x had an app that allowed you to launch any app/program by configuring a gesture, but again I didn't use it.
I guess it's just easier to place my thumb than to move about when holding the phone in one hand. Is this an idea you were thinking of implementing yourself, or are you looking for someone to pick the idea up and run with it?
Click to expand...
Click to collapse
Are you talking about lmt? Fyi: it's now also available for android/gsn...
http://forum.xda-developers.com/showthread.php?t=1330150
Sent from my Galaxy Nexus
Shaquiel Harris said:
I lost the menu button (honestly the most used button on all my other phones).
Click to expand...
Click to collapse
You never lost the menu button, it's just not on screen 100% of the time anymore, where it would just waste space otherwise.
I think its great idea!
Another few things that would be cool to see would be, resizing the Navigation Bar to be maybe a little thinner, and being able to slide the nav bar left or right, to reveal a icons to launch other apps, and maybe swiping down to hide the navbar all together.
Like you said being able to customize android and change every aspect of it is what makes this OS so awesome.
You guys ever use gesture area on webOS phones? Much better than using back key, would be a great idea. It also used visual feedback so a white line would go in the swipe direction. Currently the only phone using something similar to this is the N9 probably, which has swiping through the sides of screen to control apps.
I was just thinking about WebOS when reading this as well. Would be nice.
Just having the soft keys area as a gesture area? cool!
Maybe you could customize your gestures?
A big thing to me would be the ability to have a fully loaded package and be able to switch between stock softkeys, added search/menu softkeys, and gestures. Everything customizeable by user rather than through flashing?
menu bar like in windows 8
I think gesture is pretty good, but i`d like to see menu bar(home, recent, etc) like in win8: it is hidden until you swype from bottom-outside up, than it become unhidden. see any wideo with windows 8 tablert, you`ll see what i mean.
MrBIMC said:
I think gesture is pretty good, but i`d like to see menu bar(home, recent, etc) like in win8: it is hidden until you swype from bottom-outside up, than it become unhidden. see any wideo with windows 8 tablert, you`ll see what i mean.
Click to expand...
Click to collapse
That would get annoying pretty quickly. I don't want to have to add extra steps to navigate my phone. Back, home and recent app are buttons you use all the time, why add a barrier to get to em? More screen real estate isn't worth the extra hassle.
Enhanced said:
That would get annoying pretty quickly. I don't want to have to add extra steps to navigate my phone. Back, home and recent app are buttons you use all the time, why add a barrier to get to em? More screen real estate isn't worth the extra hassle.
Click to expand...
Click to collapse
How about navigational controls similar to the quick controls in the stock browser? Touch the bottom edge of the screen and out pops a semi-radial menu that can contain: back, home, recent apps, menu, search and can be used to add quick shortcuts to your most used apps like messaging, contacts, browser, etc., or app specific commands, like say refresh for browser, check mail for, well, email, and so on. Touching the edge requires less effort and movement as compared to swiping up or down.
I came to Android from webOS after HP shot themselves in the foot several times and one of the things I miss most is the gesture bar you had at the bottom of the screen. With the advent of the soft button area in ICS I see a real option to enable the area to work in a similar fashion. Hell yes!
The webOS gestures were:
A single swipe up would show you your running apps.
Swiping 2 fingers up would show you the launcher (app drawer).
A leftward swipe would go back.
A full swipe across the entire area going either right or left would take you to the next or previous running app.
Besides the wireless charging, the gesture area was one of the webOS killer features you very quickly learned to take for-granted. So long as gesture detection was implemented well I don't see why you couldn't have the soft buttons as they are now and gestures all working at the same time.
Call me old fashioned, but I also don't like the gestures idea.
Dolphin is just about the only program on android that I have tried to use gestures with, and it's not the sort of feature i'd personally like integrated into my phone.
That said, customizing how different people can use their phones, within the same operating system, so two people can use the exact same phone in two totally different ways, is the way to go
j.go said:
How about navigational controls similar to the quick controls in the stock browser? Touch the bottom edge of the screen and out pops a semi-radial menu that can contain: back, home, recent apps, menu, search and can be used to add quick shortcuts to your most used apps like messaging, contacts, browser, etc., or app specific commands, like say refresh for browser, check mail for, well, email, and so on. Touching the edge requires less effort and movement as compared to swiping up or down.
Click to expand...
Click to collapse
I like your idea of having the pie control from the stock browser available all over android. I had the idea a while back but was just too lazy to implement it. Today I did a small working prototype and I think I will add the pie control feature to my gesture app "LMT"...
good idea but put ot optionaly! maybe it is not practical ! iwould rather hidden button ! like Video player amaing full screen with hidden buttons !!
Huntlaar said:
good idea but put ot optionaly! maybe it is not practical ! iwould rather hidden button ! like Video player amaing full screen with hidden buttons !!
Click to expand...
Click to collapse
If implemented properly, you might be able to do away with the bottom bar and take advantage of the full screen. You can't see it with the nexus browser, but if you have a tablet running ICS and enable browser quick controls, the app hides the tabs and address bar, instantly adding an inch of usable screen real estate at the top.
Sent from my Galaxy Nexus using XDA App
The big nasty problem with having hidden buttons or, for that matter, any trigger point area(s) on the devices main screen is you'll always end up triggering something when you didn't want to or it interferes with a ui element in one or more apps e.g. game scroll bars / buttons. I've tried plenty and they all interfered with one app or another to the point I stopped using them.
The quick controls idea is fine but you're still having to watch what you're doing. The beauty of gestures in webOS was that you wouldn't have to take your eyes of what you were doing to find a button - your finger just flicked below the screen content while your eyes looked towards what you were going to do next.
I realise it's hard to imagine if you've never done it before but (weak analogy approaching...) think of it like walking up a thin and narrow set of steps as opposed to thick wide ones while trying to read a book. On the narrow steps you have to look down to hit the next step thus breaking the flow of your reading. While on the bigger wider ones you can carry on reading as the step is big enough your foot can find it without taking your eyes of your book.
Anyroad, IMHO, gestures need to be out of the way of app content so as not to interfere with app usage patterns and shouldn't require the user to take their eyes off what they're doing.
I'm hoping the discussion in this thread can inspire devs to really tweak Android.
An article I read a while back through Daring Fireball really got me thinking on how to fix the back button. This quote in particular:
They’ve replaced dumb hardware buttons with equally dumb software buttons.
Click to expand...
Click to collapse
http://daringfireball.net/linked/2012/01/16/android-buttons
This is also a good discussion on the topic:
http://www.theverge.com/2012/4/10/2...uidelines-update-settings-navigation#98209921
This is what I've come up with:
The back button should be dimmed or not visible at all when looking at the home screen.
This should also be the case for looking at the home/main scene of an app, for this reason:
The back button should never take you out of an app to the home screen, that is what the home button is for.
Instead of using the back button to close apps, use the task switcher to swipe away and actually close unwanted apps.
I know all this is possible, I just don't know how feasible it would be. I would love to see these changes in Android, what do you think?
I actually use the back button to exit out of applications, this way the app get's a chance to save any information to files. if it's forced closed, these writes can sometimes get missed and cause inconsistencies in the app (or lost time if game progress is not saved).
Having it on the home screen maintains a consistent look that many people appreciate. What i find is fantastic now is how the button rotate to the right place regardless of orientation, I KNOW that if I'm in landscape, the buttons will always be on the right hand side.
The buttons also dim down to dots in some applications (not sure if it's a new API) look at the camera app to see this in action. This removes the aesthetics of the bright buttons while leaving the functionality.
I guess you can argue about anything these days. The software keys will work better as apps are updated to 4.0 API, but to get full use out of them use AOKP, or just remove them altogether and use LMT's Pie menu. Problem fixed.
If the user accidentally opens an app, it wants to go back to where he was before. If the user opens Maps from the Gmail app, and the user wants to go back, the only way to do so is by pressing the back key.
If the user is in the App Drawer, accidentally opens an app, it wants to go back to the app drawer, and not back to the home screens.
The home button doesn't close the app, but tells the app that it's moved to the background.
The back button closes the app, tells the app it is being destroyed and lots of memory will be given back to the system.
With Android, it's possible to open app X within app Y(if the developer of app Y wants the user to do so). It wouldn't make any sense if the user had no way to undo that operation.
In my opinion, the navigation buttons are used properly.
EDIT:
Matridom said:
I actually use the back button to exit out of applications, this way the app get's a chance to save any information to files. if it's forced closed, these writes can sometimes get missed and cause inconsistencies in the app (or lost time if game progress is not saved).
Click to expand...
Click to collapse
The Android Documentation states that developers should save their data when onStop is called. onStop will be called both when user presses the home button, and when users presses the back button. So in theory, both buttons should work fine.
The buttons also dim down to dots in some applications (not sure if it's a new API) look at the camera app to see this in action. This removes the aesthetics of the bright buttons while leaving the functionality.
Click to expand...
Click to collapse
Yes, that's an API. It's possible to dim those buttons in some apps(like gallery/camera), and it's also possible to hide those buttons. The buttons will re-appear as soon as the user touches the screen. Look at the YouTube app if you want to see the buttons disappear and re-appear.
fifarunnerr said:
If the user accidentally opens an app, it wants to go back to where he was before. If the user opens Maps from the Gmail app, and the user wants to go back, the only way to do so is by pressing the back key.
If the user is in the App Drawer, accidentally opens an app, it wants to go back to the app drawer, and not back to the home screens.
The home button doesn't close the app, but tells the app that it's moved to the background.
The back button closes the app, tells the app it is being destroyed and lots of memory will be given back to the system.
With Android, it's possible to open app X within app Y(if the developer of app Y wants the user to do so). It wouldn't make any sense if the user had no way to undo that operation.
In my opinion, the navigation buttons are used properly.
Click to expand...
Click to collapse
I agree. I dont think it is "broken". It works well for me and I hate using my friend iPhone because it doesnt have a back button and I have to find it on screen.
Matridom said:
I actually use the back button to exit out of applications, this way the app get's a chance to save any information to files. if it's forced closed, these writes can sometimes get missed and cause inconsistencies in the app (or lost time if game progress is not saved).
Click to expand...
Click to collapse
I'm not talking about force closing apps, just regularly exiting apps only when they are swiped away from the multitask menu. I agree with everything else.
miketoasty said:
I guess you can argue about anything these days. The software keys will work better as apps are updated to 4.0 API, but to get full use out of them use AOKP, or just remove them altogether and use LMT's Pie menu. Problem fixed.
Click to expand...
Click to collapse
I'm not talking about removing the icons altogether, just make them contextually aware.
fifarunnerr said:
If the user accidentally opens an app, it wants to go back to where he was before. If the user opens Maps from the Gmail app, and the user wants to go back, the only way to do so is by pressing the back key.
Click to expand...
Click to collapse
This isn't the case anymore with ICS. I think the multitask button should be utilized instead. Granted, it's one extra tap, but I think it's more consistent.
fifarunnerr said:
If the user is in the App Drawer, accidentally opens an app, it wants to go back to the app drawer, and not back to the home screens.
Click to expand...
Click to collapse
I don't think that should happen. I realize that I'm arguing against actions Android has done since it's inception, but I believe that they are wrong now.
fifarunnerr said:
The home button doesn't close the app, but tells the app that it's moved to the background.
Click to expand...
Click to collapse
The home button shouldn't close an app, they should never have to unless the system decide when it needs to close an app, or the user does by swiping it away.
juliano_q said:
I hate using my friend iPhone because it doesnt have a back button and I have to find it on screen.
Click to expand...
Click to collapse
The same is for me as well, muscle memory is much faster. I just think the potential of the virtual back button is not even being scratched at yet.
thereddog said:
This isn't the case anymore with ICS. I think the multitask button should be utilized instead. Granted, it's one extra tap, but I think it's more consistent.
Click to expand...
Click to collapse
In Android, there are 2 ways of launching an app:
- As a new Task, this will add the app to the multitask interface
- As the same task, the new app won't be added to the multitask interface.
If you would like to see the second one, go to the Play Store, and click on the Email button. The Gmail apps opens. Now press the home button and open the multitask interface. You won't see the Gmail app, only the Play Store. If you open the Play Store, it'll open the gmail app, since it's the same task.
Press the home button again, and open the Gmail app(from the app drawer). The draft of the Play Store email won't show up, but it'll open the Gmail task that you opened before(for example, your latest received mail).
So, the multitask button won't work properly when the second way of launching an app is used.
The home button shouldn't close an app, they should never have to unless the system decide when it needs to close an app, or the user does by swiping it away.
Click to expand...
Click to collapse
In some cases, the back button would fit better. When you're in the Paypal app and want to close it, it's much easier to press the back button(then the user logs out), instead of pressing home, multitask button, and swipe away(thats 3 times as much time/energy).
In Android, there are 2 ways of launching an app:
- As a new Task, this will add the app to the multitask interface
- As the same task, the new app won't be added to the multitask interface.
If you would like to see the second one, go to the Play Store, and click on the Email button. The Gmail apps opens. Now press the home button and open the multitask interface. You won't see the Gmail app, only the Play Store. If you open the Play Store, it'll open the gmail app, since it's the same task.
Press the home button again, and open the Gmail app(from the app drawer). The draft of the Play Store email won't show up, but it'll open the Gmail task that you opened before(for example, your latest received mail).
So, the multitask button won't work properly when the second way of launching an app is used.
Click to expand...
Click to collapse
I actually agree with this. The back button would be used to to back into the store. GMail was never really opened though so it wouldn't have to be closed.
When you're in the Paypal app and want to close it, it's much easier to press the back button(then the user logs out), instead of pressing home, multitask button, and swipe away(thats 3 times as much time/energy).
Click to expand...
Click to collapse
In this case, I believe it is up to PayPal to have a Log Off button on the main scene of their app, and possibly in a context menu in other scenes.
although I get your main premise, I think it might be extra confusing when you have buttons just "randomly" disappearing and reappearing.
martonikaj said:
although I get your main premise, I think it might be extra confusing when you have buttons just "randomly" disappearing and reappearing.
Click to expand...
Click to collapse
Maybe not disappear, dim would work
thereddog said:
Maybe not disappear, dim would work
Click to expand...
Click to collapse
Possibly. But I think what you're looking for is a fundamental reworking of the OS here. The "Back" button is meant to work a certain way (completely at the OS level), and changing that changes everything.
What you're really looking for is the iPhone setup, where all you have is a "Home" and "Multitasking" (just double tap home, could be a separate button). All "Back" functions are handled at the app level, not the OS level. Back buttons are placed at the discretion of the developer.
The consistency provided by the Android way of handling "Back" at the OS level has many advantages I think.
The software keys actually work great. I've never had a problem with them. The menu key always comes up when its needed and I'm not finding myself missing the search key either.
Sent from my Galaxy Nexus using XDA
the whole back button talk has got me thinking. do you guys think the back virtual button will go away any time soon since the new style guides want a back button in the top left corner.?
The way the android back button works is simply brilliant and I hope it never changes. The application stack is very thoroughly thought out and designed for a specific reason. As already mentioned there are many examples/situations that wouldn't be possible if there was no activity stack history with the back button function. You just have to learn how the activity stack works.
And yes you should ALWAYS use the back button to leave an app, never home. It clears that activity stack. Only time to use home is when you want to background said app to come back to later, ie multitasking.
I pray to god they don't change the way the back button functions. I like having all my keys lit up whenever I'm not using a full screen application. I like that the back button goes through different apps/pages when you close out of it. This just integrates multi-tasking soooo much better. I don't want to have to wade through different clicks and apps just to get to a place I was before (i.e. backing into a different application). I'm not sure I understand the premise of this... please elaborate?
It is entirely possible to implement this in the OS, it's just a question if Google wants to do this. I personally am well adapted to Android's back button, and find it much better for multitasking than Apple's iOS design. Example:
1. Open Twitter, click on link from Tweet
2. Android opens the browser, I read whatever was posted, then hit back
3. I return to my Twitter feed, ready to move onto the next Tweet
This works in a multitude of apps, from Reader to Google Music to anything that wants to keep the previous app alive in the background. Can you imagine having a back button in the Browser that could both take you back a page and also take you back to the app you used to launch it? Apple's iOS solves this by eliminating any form of efficient multitasking in my opinion, as you have to double press home and select the previous app. The iPad does it better with gestures, but a soft back-key would easily suffice.
Additionally, Apple's iOS also has a varying design for the back-key, it's in different places for different apps. I personally love the static back-key on Android, and I've used both on a daily basis. You could dim the back button when on the home screen, but that would leave a gaping hole in the Navigation bar, in addition of wasting RAM/Processing power continuously disappearing and reappearing the key when you move from home-screen to app.
You guys using them?
It is good and I wanted to use them badly but one main thing I am missing is the additional gestures that the navigation buttons had with them.
I use to double tap on recent button to switch screen off which is not possible to do with new gestures.
Having additional app or using the physical button is what I wanted to avoid.
have been using them long time ago with the app swipe navigation. Works perfectly once you get used to it.
I'm a minimalist. I have my dock & notification bar hidden also. Love that clean approach. Best part is if anyone finds/steals it, that are clueless.
Has there been a port of the new swipe guestures to nougat? I'm on 7.1.1
I am using gesture swipes, it is nice way to use phone without buttons... For double tap to lock, there is way if you are using Nova for example.....
With Beta 7 you can double tap to sleep without nav bar
You lose all of the additional gestures you have with the navbar, but in my opinion it looks way cleaner and really emphasizes the big display. And also one less spot risking permanent burn-in!
While I do like the off-screen gestures, and do use them, I actually prefer Motorola's gestures where you can quickly 'wave' you're phone in the air and the flashlight turns on, or how you can give the phone a flick and the camera app open. It's faster IMO.
But I still would prefer a Oneplus 5t over any Motorola anyday.
Love em, with an advanced launcher like Action or Nova you've got a ton more gestures that can be assigned covering the lost shortcuts on the nav buttons and then some. Speaking for myself I've got leftover swipes and taps that remain unassigned and can get to anything I use with regularity with a single touch. I liked some of the Motorola stuff myself, like Oneplus they've kept to a mostly stock experience with genuinely useful adds that don't detract from the "stockness". For some reason I really liked being able to change the ok google command to whatever I wanted and that would probably be my top pick if Oneplus were to, ahem, borrow, something from them.
Disabled them all got tired of accidentally turning the flashlight on
What I think would be the most useful feature is iPhone's double tap (not click) to bring down UI on top. Android should support this native long ago...
Needs tweaking..Still using xposed edge gestures, because I'd like for swipe up Near back button for back, swipe up near home bottom to home, and swipe up near recents to recents. i only use this mode to disable annoying nav bar easily
Siljorfag said:
What I think would be the most useful feature is iPhone's double tap (not click) to bring down UI on top. Android should support this native long ago...
Click to expand...
Click to collapse
This can be done with many of the launchers although swipe down (anywhere) fits in better with the notification shade as it already expands via swipe down. I suspect the reason it and many other things aren't standard is a lack of consensus. With the shade already working with swipes many of us have double tap allocated elsewhere the most common usage probably being for sleep and wake purposes.
It's always hard to tell the level of experience users have so don't take this the wrong way... Your post suggests you might want to consider taking a few launchers for a test drive because no matter what you like there is one that works better than what came stock.