The webOS Wish List: Lockable Cards | webOS Nation
 
 

The webOS Wish List: Lockable Cards 17

by Derek Kessler Thu, 03 Jan 2013 7:29 pm EST

The webOS Wish List: Lockable Cards

If you're like me (and who doesn't want to be like me?), your webOS device is constantly full of multitasking app cards. Some are fleeting, around for until you don't need them anymore and then tossed off the top of the screen like the day's garbage. Others are important, and you keep them around because you don't want to deal with relaunching the app later, need it to be running in the background, or just want to have whatever's in that card available for quick reference later. For that latter category of app cards there's a problem lurking in your quick-gesturing thumb: the inadvertent toss-away.

It's too easy, we know. You're busy closing away unneeded cards at the end of the day and before you know it you've tossed away the web browser card with that restaurant address you were going to need later that evening. Curse words fly forth as you're forced to reopen the browser, dig into your history, and find the lost page. But… what if you could lock that card and make it so you couldn't accidentally throw it away? Wouldn't that be grand?

Yes, it would indeed be exceedingly grand. But locking a card should be a very deliberate action, something you can't do or undo accidentally. Our simple and straightforward proposal: pull down and hold. The current pull-down behavior in webOS varies depending on the version. webOS 1.x and 2.x treat a pull down the same as tapping on a card, merely maximizing the card. It makes sense - if pushing it away is closing it, pulling it down - towards you - should be the opposite, making the card active. But webOS 3.x left us scratching our heads, as pulling down on an app card instead triggers a slingshot that throws it off the top of the screen, closing any background processes for running built-in apps. Useful, but in no way intuitive.

So our proposal is really two-fold. First: restore the pull-down-to-open behavior for cards. Second: add a pull-down-and-hold gesture to trigger locking a card. For a visual cue, add a red glow and a lock icon on activation, and have a translucent lock icon superimposed on the locked app in card view. Swiping up on a locked card triggers a vertical wobble (perhaps with a red glow at the top of the screen), and unlocking is accomplished by the same pull-down-and-hold gesture.

Simple, intuitive, discoverable, and it doesn't get in the way if you don't need it. Most of all, it's useful and a life-saver of sorts.

Have your own thoughts on this or any other webOS Wish List entry? We'd be disappointed if you didn't. That's why we have the comments, it's your place to say how incredibly right (or horribly wrong) we are, plus there's a poll! And we have little doubt you have your own ideas as to what ought be on the webOS wish list, and so there's a forum thread just for that where awesome webOS dreaming is the order of the day.

17 Comments

Its a great idea, but I have to say after all these years I have thrown a card away by mistake maybe once. Its a pretty deliberate action.

What I really want is to be able to choose where new cards open. For example one could have all the ones that use all day in a stack to the right and all new one open to the left. For organization in my mind

But for sure lockable cards would add to the solidness of webos as an operating system.

Webos Wish List:
Auto correct working in browser, like writing this comment for example, selecting a suggestion does nothing

Rotating emails and texts in notification area. Don't want to have to open app to see what the other ones are

Ya... I hated the fact I tossed out all my cards n even the important one. So this would be a great idea.

How you manage that? You just start tossing off the screen without looking

Should be highlited when locked n pull down again to unlock n slingshot it out the screen just like before ;)

Wish list:

What about when pulling down the card instead of opening the card (webOS 1.x and 2.x) or closing it (3.x) save it on the dashboard to use later???

Mainly for the webpages... I leave some webpages open to see later or to make some notation or whatnot and if you have to many cards open the browser cards go blank (or gray) and you need to reload them...

What if we could save them for later pulling them to the dashboard where the app is put on a "freeze" state so it doesn't use resources... or even better, when pulled to dashboard the page gets saved and can be viewed later offline...

Maybe the pull action could be made with 2 fingers instead of 1 if people like the slingshot behavior... or 1 finger saves 1 card, 2 fingers the whole stack...

still want the slingshot behavior??? ok ok, 1 finger slingshot, 2 card save, 3 stack save...

maybe the "pull card" could freeze an app for later use (maps) or send to dashboard to have minimized info (weather dashboard or music app)... depends on what the developer wants to use the dashboard for...

this has been discussed in the forums many times. Its a great idea and needs to happen now we have LunaCE and openWebOS.

http://forums.webosnation.com/2818679-post1.html

How about: One finger pull, do as you suggest. Two finger pull, use password lock. Blank out the card and write a description in small text.

My idea: ::::.
Prompt for a password when unlocking.Some or all fields would be optional as the data may not be accessable, or applicable. would be the first ten letters of the URL, filename, book, song, movie, etc, depending on the app. would be indicate if the file is finished, spreadsheet is finished calculating, new emails, again depending on the app.

Add I think slingshot should be a two finger push.

How to close an app completely then??? On the touchpad the e-mail app / picture app / agenda / contacts keep running in the background to bring the app up quickly when tapped again. (the app nevers closes, only it's card is no longer visseble). To have the pictures app refresh you sometimes have to really close it by pulling it down.

Perhaps the default apps should be fixed so they don't suck at multitasking on a system that's built around multitasking?

I don't see why we would want to be like someone that unintentionally throws cards away? :-P

I would like to bring miniature cards back. Instead of locking the card in the stack, having it take up space and block the entire screen, why not just miniaturize it and pin it to grid on the desktop? Come up with a gesture to bring up the grid and select the miniaturized apps on it when needed. I recommended this before in the forums. Now Blackberry 10 does this. I think it is a better solution.

I've thrown away a card by accident maybe once a month or so, but the times I do it, half the time I wished I hadn't. Perhaps the use case would be that thrown away cards go in a wastebasket for maybe 5 minutes so you can go fetch them if you want.

Before I got my Pre+ and switched to WebOS, I had installed TealOS on my Centro and liked how the cards were lockable.

It's rare that I've thrown away a card by accident. Far, far, FAR more common is that WebOS has done its own job of throwing away not a card itself, but its form contents. That is, if I'm in a browser or an app that uses the browser component, I'll be in middle of typing something up in a form field like this one, and SURPRISE -- some browser tab loading in the background just pushed me over some memory limit, and instead of just not loading any new stuff, some genius thought it would be a great idea to throw a translucent "scrim" and spinning circle throbber on every single damn page I have open, completely throwing away any work in progress, and loading the page afresh next time the card is selected. Disabling Flash helps make these reloads somewhat less frquent, but it doesn't eliminate them altogether. Some sites will trigger this with nothing else open, leading to periodic reloads. Infuriating. I can understand getting "too many cards- throw away some"errors occasionally -- WebOS folks may not have wanted to use flexible virtual memory with page swapping because lots of rewrites and SSDs can be problematic, but this is triggered far more frequently, generally when I shouldn't be even close to be hitting the 1GB limit of the Touchpad's active memory, so I don't know if it's some other system resource being exceeded that triggers it, or what. In any case, it's a horrible way of handling a resource limit. If they needed to have WebOS free up some memory or whatever, it should temporarily unload and scrim just the least recently used browser card, not ALL of them. (If that doesn't free up enough, scrim the next least recently viewed card, and so on.)

This a re-post (of mine) from the Forum section "webOS development".

http://forums.webosnation.com/webos-discussion/310581-webos-wish-list-13...

I'm not sure if the following has been suggested, but I'd like to see a "9 Tile" screen scenario that has up to 9 running apps / features - as is demonstrated in the photo below. It could be called "Tile mode" - for lack of a better term.

webos-9-tile-screen.jpg

The Centre app (or Dominant app) can be tapped to go full screen. Or it can be switched with one of surrounding apps, by swiping the dominant app towards that "Secondary" app (thereby making it now the dominant app). Or vice versa, by moving one of the surrounding apps towards the Centre - effectively switching places
.