Ubuntu Software Center will probably suffer from that syndrome "because
it's open". Unless they start to make a distinction between packages and
command-line applications (which are quite good anyway and won't need any
restriction) and actual desktop/phone/tablet apps (which need strict
management)
I agree completely with this statement. Even if they do think about
usability, they just don't care unless someone draws a line in the sand and
says "you have to make it at least this good."
On Tue, Jun 25, 2013 at 9:33 AM, Zisu Andrei wrote:
> I would hope it becomes obvious when those kind of
>
> I would hope it becomes obvious when those kind of things are being
> implemented.
You might be surprised how many people don't think about usability and make
crap applications. That's why Apple is so strict with their AppStore.
Zisu Andrei
On 25 June 2013 15:29, Sam Bull wrote:
> On T
On Tue, 2013-06-25 at 15:22 +0100, Zisu Andrei wrote:
> You might wanna get that into the design guidelines. Or at least
> outline some "Back button guidelines"
I would hope it becomes obvious when those kind of things are being
implemented. I'm sure Android works like that, except they have a
ha
On 06/25/2013 09:18 AM, Zisu Andrei wrote:
> Now this is my Achille's heel... I didn't try the preview. If it works
> that way then it means I just fueled a moot discussion and I'm sorry
> for that :D
Here is the link that describes how it works:
http://design.ubuntu.com/apps/get-started/ui-model/
>
> If attaching an email, and it opens the email app to do so, it would
> surely be done in a way that when you select the email it automatically
> closes and returns to the calendar.
> In other words, it acts like a dialog pop-up or something, not a
> separate app. So, you would have a 'select' a
On 06/25/2013 09:06 AM, Josh Leverette wrote:
> Then how would you get back to the main list of emails without exiting
> the app completely?
Good point, I hadn't thought about that. After considering the
right-edge back swipe as a global OS-level back action, I would say that
the per-app page stac
On Tue, 2013-06-25 at 15:05 +0100, Zisu Andrei wrote:
> Inbox. The back button is in an app, why would the back button
> exit the
> app? Nothing should take you 'back to the notifications'
> Well, see, that's where the confusion comes, I see the page stack as
> having the e
Now this is my Achille's heel... I didn't try the preview. If it works that
way then it means I just fueled a moot discussion and I'm sorry for that :D
Zisu Andrei
On 25 June 2013 15:17, Michael Spencer wrote:
> On 06/25/2013 09:05 AM, Zisu Andrei wrote:
>
> Inbox. The back button is in an a
On 06/25/2013 09:05 AM, Zisu Andrei wrote:
>
> Inbox. The back button is in an app, why would the back button
> exit the
> app? Nothing should take you 'back to the notifications'
>
> Well, see, that's where the confusion comes, I see the page stack as
> having the email page on top of
Then how would you get back to the main list of emails without exiting the
app completely?
On Tue, Jun 25, 2013 at 9:04 AM, Michael Spencer wrote:
> On 06/25/2013 08:50 AM, Zisu Andrei wrote:
>
> However, using a page stack, at least on the phone, makes the most sense
>> in my opinion, because
Does it? It doesn't always. And an email is of equal importance to the main
list of threads because you could very well want to reference other emails
while composing a new one. I've had to save an email as a draft, return to
the main list of emails, and go back to my draft countless times on Andro
>
> Inbox. The back button is in an app, why would the back button exit the
> app? Nothing should take you 'back to the notifications'
Well, see, that's where the confusion comes, I see the page stack as having
the email page on top of the notifications page, thus if it were to go back
in the stac
On 06/25/2013 08:50 AM, Zisu Andrei wrote:
>
> However, using a page stack, at least on the phone, makes the most
> sense in my opinion, because it conveys the hierarchy of the email
> layout well:
>
>
> There is one major flaw I see straightaway and which has been raised
> many times o
Presumably, to the inbox, which is what happens now on my Android device.
On Tue, Jun 25, 2013 at 9:50 AM, Zisu Andrei wrote:
> However, using a page stack, at least on the phone, makes the most sense
>> in my opinion, because it conveys the hierarchy of the email layout well:
>
>
> There is on
On Tue, 2013-06-25 at 14:50 +0100, Zisu Andrei wrote:
> There is one major flaw I see straightaway and which has been raised
> many times on this thread: you open an email from a notification, you
> tap the back button, where do you go: inbox or back to the
> notifications?
Inbox. The back button
>
> However, using a page stack, at least on the phone, makes the most sense
> in my opinion, because it conveys the hierarchy of the email layout well:
There is one major flaw I see straightaway and which has been raised many
times on this thread: you open an email from a notification, you tap t
On 06/24/2013 08:35 PM, Josh Leverette wrote:
> Why do you need a back button at all in the email app? I can actually
> think of a number of effective implementations that don't require a
> back button -- not even to return from viewing an email. However, if
> an app is making such extensive use of
>
> If you mean that it should give full screen estate to the content, to
> show as much of it as possible, then I disagree as most emails you only
> glance at and delete. The advantage of using the toolbar, is that if you
> wanted the full screen, (as long as the developer doesn't lock the
> toolb
I agree. For some apps it makes more sens to show the toolbar than to hide
it and in those cases it should be opened by default.
On Jun 25, 2013 12:01 PM, "Sam Bull" wrote:
> On Tue, 2013-06-25 at 10:48 +0100, Zisu Andrei wrote:
> > But the email view is the content view, which, if it were for
>
On Tue, 2013-06-25 at 10:48 +0100, Zisu Andrei wrote:
> But the email view is the content view, which, if it were for
> consistency, would be fullscreen (toolbar hidden).
I don't know what you mean, the toolbar is hidden by default normally,
what does a content view, or fullscreen have to do with
But the email view is the content view, which, if it were for consistency,
would be fullscreen (toolbar hidden). How would you explain having the
toolbar on *some* content views and on some not?
--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Uns
On Mon, 2013-06-24 at 16:45 -0500, Michael Spencer wrote:
> I've been tinkering around with ideas for the email app, and
> already I'm tired of having to swipe up the toolbar, click the back
> button, swipe up the toolbar, and then click the back button just to get
> to the top level.
If this is j
>
> that dynamically generates a new tab for this email thread
Isn't this a bit of a different paradigm than what we have right now?
Currently the tabs are quite rigid and I don't recall seeing any closeable
tabs.
What you present in Option B is, however, a lot better as it is virtually
the same
Why do you need a back button at all in the email app? I can actually think
of a number of effective implementations that don't require a back button
-- not even to return from viewing an email. However, if an app is making
such extensive use of the back button, there's nothing stopping the
develop
On 06/24/2013 03:47 PM, Zisu Andrei wrote:
> Too many places, variations and bla. I urge the design team to find
> only ONE size fits all, as long as it adresses Android's ugliness.
>
> That's the biggest difference between iOS and Android: consistency,
> you only have one "paradigm" that you use
Too many places, variations and bla. I urge the design team to find only
ONE size fits all, as long as it adresses Android's ugliness.
That's the biggest difference between iOS and Android: consistency, you
only have one "paradigm" that you use to get back in the app, and one home
button you use t
On 06/24/2013 03:18 AM, Michel Renon wrote:
> Hi all,
>
> I'm late to answer on this topic, but I've made some mockups :
>
> - first is about a back button in an overlay :
> http://www.mr-consultant.net/blog/wp-content/uploads/2013/06/proposal_back_button_1.jpg
>
>
>
> - second is about a back gest
On Mon, 2013-06-24 at 10:48 +0200, Oliver Grawert wrote:
> hmm,, am i the only one who finds the behavior of the gallery logical
> and natural here ?
>
> swiping from the center of the screen to the left -> back
> swiping from the center to the right -> forward
While I agree with the design of t
Yeah that's true, and I have to admit I was thinking about when the
image is pinch zoomed some amount. Indeed for an unzoomed image the
flick is natural. Getting into some grey areas when describing things
here...
Till later,
Scott.
__
Scott May.
sc...@sma
hi,
On Mo, 2013-06-24 at 19:09 +1000, Scott May wrote:
> If, by gallery, you mean you have a picture open - I'd have to disagree.
>
> If I'm looking at a picture - and I swipe from the middle to anywhere -
> I'm simply trying to pan the image (or map or web page or whatever) around.
>
> I keep s
Well, Android (and also others I think) does it like that: when you have
a picture open, and swipe it to the left or to the right, it goes to the
previous/next picture.
I wouldn't say that is has to be like this just because others handle it
like that, but at least users are used to this behavio
Hi Michel,
Thanks for doing those mock-ups - very helpful. Seeing those, I'm a big
fan of variation 2 - pull up then oblique. I think it's more consistent
with the gestures as already described.
Till later,
Scott.
__
Scott May.
sc...@smartdata.com.au
If, by gallery, you mean you have a picture open - I'd have to disagree.
If I'm looking at a picture - and I swipe from the middle to anywhere -
I'm simply trying to pan the image (or map or web page or whatever) around.
I keep saying, gestures from the edges in are pretty safe, but the main
hi,
On Do, 2013-06-13 at 17:02 +0100, Matthew Paul Thomas wrote:
> A gesture might be more efficient than revealing the toolbar then
> tapping Back. But I doubt it would be more discoverable.
>
hmm,, am i the only one who finds the behavior of the gallery logical
and natural here ?
swiping from
Hi all,
I'm late to answer on this topic, but I've made some mockups :
- first is about a back button in an overlay :
http://www.mr-consultant.net/blog/wp-content/uploads/2013/06/proposal_back_button_1.jpg
- second is about a back gesture (already proposed in this thread)
Please note that the
Hey Tony,
Yeah I think it was my suggestion you're thinking about, but I did say
up and to the left, just as the icon would suggest. Playing with the
phone more since and I'm more convinced now that this is an intuitive
gesture...
Till later,
Scott.
__
Scott M
Maybe this whole gesture thing should be left for someone like Ubuntu Tweak
to implement? Surely Ubuntu touch will give users root/sudo access by
default, just like on the desktop version, so there's absolutely no reason
this can't be done after the fact. I don't believe there will be enough
page s
What I was thinking when I wrote the mail with that motion, was that the
page you're currently on follows your thumb when you move it to the right.
The "previous" page (the page you're going to) can be either in the back of
the current page (with some shadows, so it is clear that the current page
i
> Someone suggested a swipe up and to the right ( in one motion ), whereas
> the "back" button actually shows an arrow that goes up and to the left.
> Seem like a pretty intuitive gesture to me...
>
> Does our touch framework support this kind of a pattern-style gesture?
This would actually be pr
On 06/13/2013 12:02 PM, Matthew Paul Thomas wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Scott May wrote on 12/06/13 12:33:
>>
>> Yeah I'm a "me too" on the concern that the "back" button is too
>> hidden given it's frequent use. Perhaps we won't need "back" so
>> much in this ne
I agree, I didn't want to be the only one who keeps dissenting, so I
waited, but the right edge swipe should not behave like Android's.
Furthermore, it would be highly unintuitive for it to go back pages in the
app and then suddenly switch to going to previous apps. Once it reaches the
first most p
On Sat, Jun 15, 2013 at 5:17 AM, Rasmus Eneman wrote:
> Personally I have been thinking about how it would be to rework the right
> edge swipe. If it first backed out to the topp level and then start
> circulating apps, a bit like Androids back button. For me that's the most
> natural behavior I
>> Android, WebOS or any new system.
>> > >>>
>> > >>> Sidenote on back button actions. Short swipe up shows the menu, what
>> > >>> does
>> > >>> a long swipe up do? Could a long swipe up be use for "Back” action?
>&g
> > >>> part. So backing out to a common are is what's needed most the time
> even
> > >>> if
> > >>> its only one level deep.
> > >>>
> > >>> What do you all think?
> > >>> Thank you and God
ich
> >>>> works
> >>>> for all situations, rather than creating fragmentation in the UI by
> >>>> letting
> >>>> individual dev's make too many choices.
> >>>>
> >>>> 1. Use the developer’s tool
t; letting
> >>>> individual dev's make too many choices.
> >>>>
> >>>> 1. Use the developer’s toolkit
> >>>>
> >>>>
> >>>> Here is our handy developer’s toolkit which contains all the e
don’t carry other platform’s UI elements or behaviours.
>>>>
>>>>
>>>> /\ http://design.ubuntu.com/apps/get-started/make-it-ubuntu
>>>>
>>>>
>>>> I've just uploaded a short clip of the Evernote app on iOS, the way i
n, reveals on scroll up), which is _only_ implemented on
>>> deep page stack pages would be my suggestion. As far as I can see from the
>>> design spec, no other page types have this 'back' problem. See this link
>>> for the various page types >
>&g
gt;>
>>
>>
>>
>> On 13 Jun 2013, at 18:18, Omar B. wrote:
>>
>>> Some apps don't have a problem with users going "back". For example
>the *Friends* app shows both its Breadcrumbs and the bottom toolbar by
>default:
>>>
>>> http
gt;
>> Apps should probably decide if they want to show these toolbars by default
>> (or when one goes deeper in the stack like others mentioned) if its better
>> for their users (and allow users to hide them if they want more screen). I
>> think this approach might be be
ote:
>>
>> Some apps don't have a problem with users going "back". For example the
>> *Friends* app shows both its Breadcrumbs and the bottom toolbar by default:
>>
>> http://youtu.be/Q566IGyVB0o?t=8m36s
>>
>> Apps should probably d
its better for their users (and allow users to hide them if they want
>more screen). I think this approach might be better than trying a "one
>fits all".
>>
>> Regards.
>>
>> > Date: Thu, 13 Jun 2013 17:02:58 +0100
>> > From: m...@canonical.com
&g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/13/2013 07:02 PM, Matthew Paul Thomas wrote:
> Discoverability of "Back" is my biggest concern with System
> Settings right now. In a couple of cases I've specified that the
> toolbar should be visible all the time: for example, the screen for
>
: Thu, 13 Jun 2013 17:02:58 +0100
> > From: m...@canonical.com
> > To: ubuntu-phone@lists.launchpad.net
> > Subject: Re: [Ubuntu-phone] [Design] Page stack back gesture
> >
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > Scott May wr
: ubuntu-phone@lists.launchpad.net
> Subject: Re: [Ubuntu-phone] [Design] Page stack back gesture
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Scott May wrote on 12/06/13 12:33:
> >
> > Yeah I'm a "me too" on the concern that the "back&
> A gesture might be more efficient than revealing the toolbar then
> tapping Back. But I doubt it would be more discoverable.
>
My suggestion would be just to show the toolbar by default on all page stack
pages aside from the 1st page in the stack.
The way I see it is all those pages beyond
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Scott May wrote on 12/06/13 12:33:
>
> Yeah I'm a "me too" on the concern that the "back" button is too
> hidden given it's frequent use. Perhaps we won't need "back" so
> much in this new environment?
The System Settings design uses deep page stac
On Wed, 2013-06-12 at 14:41 +0100, Lou Greenwood wrote:
> If it's appropriate for settings, email etc, why not for all? Doesn't
> that just add even more confusion?
Because these are the exceptions to the rule, the only ones that need
frequent access to controls. When viewing email, it is common
If it's appropriate for settings, email etc, why not for all? Doesn't
that just add even more confusion?
The point of hiding these controls, is to give more screen estate to the
app, instead of using it to display buttons which are not frequently
used.
My point is that it seems that these ar
I took what Sam said and just tried everything I thought I'd need to
(that I can so far) and yeah, "back" wasn't as important as it is in
Android - to my mind. I think expansion, those carousel devices on the
people page remove the need more that I thought. I still like my
gesture "swipe from
On Wed, 2013-06-12 at 14:07 +0100, Lou Greenwood wrote:
> Email
> Calendar
> Todo app
> Settings
> Contacts
> Phone
> Messages
OK, so phone doesn't use the back button.
If contacts used the same design as the people lens (which is
practically the same thing anyway) it wouldn't use a back button.
Just curious, but what part of the update made your opinion change? I think
this issue is resolved for now though.
On Wed, Jun 12, 2013 at 8:08 AM, Scott May wrote:
> To be honest I've not updated my Nexus to a recent image (until just
> now!) since we're approaching the "dog fooding" stage.
To be honest I've not updated my Nexus to a recent image (until just
now!) since we're approaching the "dog fooding" stage. Anyway I did and
my opinion may have changed.
I think "Expansion" is probably something we're not so familiar with as
programmers and user interface designers, but will
Hi Sam,
That's exactly my point, that it should not be system wide, but only in
the instances where the back button is necessary (specifically deep
'page stack' pages). It's outlined in the design spec, so the designers
expect it to be used. Judging by the number of differing opinions on
this
This sounds reasonable to me.
Sincerely,
Josh
On Jun 12, 2013 7:52 AM, "Sam Bull" wrote:
> On Wed, 2013-06-12 at 13:37 +0100, Lou Greenwood wrote:
> > See the following link for examples of the back button in the core OS.
> >
> > http://design.ubuntu.com/apps/building-blocks/page-stack
>
> I've
On Wed, 2013-06-12 at 13:37 +0100, Lou Greenwood wrote:
> See the following link for examples of the back button in the core OS.
>
> http://design.ubuntu.com/apps/building-blocks/page-stack
I've been running the system on my phone for nearly 4 months, I know
where the back button is. I also know
On Wed, 2013-06-12 at 07:27 -0500, Josh Leverette wrote:
> None of Ubuntu's gestures are discoverable, that's just the hard
> reality of it.
I suspect you're right, that they will need a brief first-boot tutorial.
But, if you know that Ubuntu Touch uses all the edges, just with that
one piece of k
Hi Sam,
See the following link for examples of the back button in the core OS.
http://design.ubuntu.com/apps/building-blocks/page-stack
Cheers
On 12/06/13 13:24, Fola Dawodu wrote:
I doubt if anyone can discover pin to exit gesture on their own.
meaning its not exactly intuitive.
But the
Hi Josh,
I don't think there's anything wrong with it at all, in fact I think
it's a nice, precise gesture for certain actions. However, I don't think
that it, or any other gesture, solves the core problem that it is not
obvious or easy to navigate backwards form a deep page stack page. The
i
None of Ubuntu's gestures are discoverable, that's just the hard reality of
it. The only way this is ever going to work is if the team puts a
first-boot tutorial that walks you through each of the gestures and makes
you practice them (with a skip option for people who already know what
they're doin
I doubt if anyone can discover pin to exit gesture on their own. meaning
its not exactly intuitive.
But the again, if i may recall the design paradigm for Touch actually
does not envisage this problem as a general thing (i'm pretty sure i'm
wrong though)
meaning that this really should be an
What's wrong with the Pin to Exit gesture? It will not be accidentally
discovered by old people in all but the most unlikely scenarios, the
toolbar already provides a back option for them, and power users would
benefit from having a faster and perhaps more elegant way to go back. It's
quick and doe
On Wed, 2013-06-12 at 10:11 +0100, Lou Greenwood wrote:
> I imagine that the page stack will be a very common view, having to
> swipe up and then stretch and tap, just to go back, could become
> fatiguing. Perhaps once I get my hands on a working set-up my concerns
> will be unfounded.
Just an
Whilst I initially raised the gesture idea as a way to get around the
lack of a back button, I think that this discussion has raised some very
valid objections to gestures, specifically from Scott & folabiklan.
I think the true solution is to show the toolbar by default on the deep
page stack
e and
>> especially on tablets.
>>
>> The button may stay hidden and be invoked upon tapping a particular
>> section on the screen.
>> ,
>> Sent from my android device.
>>
>> -Original Message-
>> From: Simon
>> To: ubuntu-phone@list
ay stay hidden and be invoked upon tapping a particular
> section on the screen.
> ,
> Sent from my android device.
>
> -Original Message-
> From: Simon
> To: ubuntu-phone@lists.launchpad.net
> Sent: Wed, 12 Jun 2013 12:45 PM
> Subject: Re: [Ubuntu-phone] [Desig
Just one more time, please Daddy... Sorry. Okay so this has to work on
tablets too. Squeezing the sides of the screen is too hard there.
What about a gesture: Drag from the bottom edge (which will bring up the
bottom menu) and just continue up and across to the left edge. One
simple gestur
Simon, This would introduce design complexity by the way that the user may
accidentally activate this gesture or fail to activate this gesture and
have negative consequences. It needs to be something that does not interact
with the current gestures, unless we're willing to drop an existing gesture
Message-
From: Simon
To: ubuntu-phone@lists.launchpad.net
Sent: Wed, 12 Jun 2013 12:45 PM
Subject: Re: [Ubuntu-phone] [Design] Page stack back gesture
--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu
"Last one for a while I promise. What about a pinch from both the left and
right sides - together, like I'm closing up this page 'cause I'm done with
it"
If I may this is more of "close this app gesture", however I'm not sure
when somebody really needs a back button since swiping from right gives
Since "Swiping from the right" is meant to change to a (previously used)
app,
we could extend this gesture to somehow integrate a "back"-option.
For example we could swipe from the right side to the top-right (or
bottom-right) corner and activate the "back"-action this way?
signature.asc
Descr
I'd be fine with a title bar button, but I don't know how it could be
done... the current design isn't conducive to that. But, Pin to Exit is the
way to go, in my opinion. Does anyone else have feelings for or against Pin
to Exit, as described in my previous email?
Sincerely,
Josh
On Jun 12, 2013
Last one for a while I promise. What about a pinch from both the left
and right sides - together, like "I'm closing up this page 'cause I'm
done with it"
Good night all :)
Till later,
Scott.
__
Scott May.
sc...@smartdata.com.au
Mobile 0417 195 018
I haven't considered the full screen situation. Sorry about that.
Still thinking...
Till later,
Scott.
__
Scott May.
sc...@smartdata.com.au
Mobile 0417 195 018
On 12/06/13 21:33, Scott May wrote:
Yeah I'm a "me too" on the concern that the "back" but
Yeah I'm a "me too" on the concern that the "back" button is too hidden
given it's frequent use. Perhaps we won't need "back" so much in this
new environment?
In any case, with gestures we need to be very mindful of how apps are
going to operate. We don't want to offer a gesture that might l
me features
>> in the Android and Win8 homescreens that can be pinched to give an overview
>> on them.
>>
>> For the particular case of the pictures app', we'll have problems to
>> combine it with zooming/unzooming the picture we are looking at.
>>
&g
en with the whole hand, as
we'd take away the upper paper of a stack.
Congrats for the work done so far, and good luck with the
upcomming tasks !
Clément
> Date: Wed, 12 Jun 2013 10:11:51 +0100
> From: lougreenw...@me.com <mailto:lougreenw...@me.com>
> To:
actually, at this point, I really don't know the solution. I think the
Design team should give it some thought and get back to us afterwards.
Sincerely,
Josh
On Jun 12, 2013 6:15 AM, "Josh Leverette" wrote:
> let's stick with pinch zooming our way back out if we absolutely must. I'd
> recommend
let's stick with pinch zooming our way back out if we absolutely must. I'd
recommend just redesigning the title bar element to have a back button.
Sincerely,
Josh
On Jun 12, 2013 6:12 AM, "Josh Leverette" wrote:
> I would like there to be such a gesture, I'm just not convinced there's an
> appro
I feel the same way a left to right gesture from anywhere other than the
edge would be our best option for a back gesture.
On Jun 12, 2013 6:12 AM, "Josh Leverette" wrote:
> I would like there to be such a gesture, I'm just not convinced there's an
> appropriate one since the left edge of the scr
Can you distinguish shake gestures? Otherwise I'm afreight that it wont
work. What happens when you are on a train or a bumpy road? Back, back,
back ...
We could also think about using shaking for going back.
This would be doable with just one hand,
and wouldn't conflict with other (and future) ges
I would like there to be such a gesture, I'm just not convinced there's an
appropriate one since the left edge of the screen is occupied. My
suggestion is we consider that swiping from left to right anywhere not on
the screen edge could act as a back gesture in most applications.
I caution strongl
At the moment the "back" and other browser-/has happened upon bringing up
the HUD. it's working at times with the Facebook "app".
Maybe something similar to bringing the HUD up could be implemented as some
kind of visible gesture to make it able to go back in one stroke.
On 12 Jun 2013 18:25, "Sim
We could also think about using shaking for going back.
This would be doable with just one hand,
and wouldn't conflict with other (and future) gestures which are
touch-based.
0x7CA11280.asc
Description: application/pgp-keys
signature.asc
Description: OpenPGP digital signature
--
Mailing list:
e whole hand, as we'd take away
> the upper paper of a stack.
>
> Congrats for the work done so far, and good luck with the upcomming tasks !
>
> Clément
>
> > Date: Wed, 12 Jun 2013 10:11:51 +0100
> > From: lougreenw...@me.com
> > To: ubuntu-phone@lists.
one so far, and good luck with the upcomming tasks !
Clément
> Date: Wed, 12 Jun 2013 10:11:51 +0100
> From: lougreenw...@me.com
> To: ubuntu-phone@lists.launchpad.net
> Subject: [Ubuntu-phone] [Design] Page stack back gesture
>
> Hi all,
>
> This is my first contribution
Hi all,
This is my first contribution to the list. I've only recently discovered
the Ubuntu Phone effort, but it looks like it will be very interesting,
powerful & beautiful, kudos to the artists!
I've just been looking through the design guidelines for Ubuntu Phone
and something stuck out t
98 matches
Mail list logo
