Received: by 10.90.55.17 with SMTP id d17mr12897782aga.12.1279179023364;
        Thu, 15 Jul 2010 00:30:23 -0700 (PDT)
X-BeenThere: chromium-a...@chromium.org
Received: by 10.91.21.28 with SMTP id y28ls311336agi.2.p; Thu, 15 Jul 2010 
	00:30:20 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.91.59.20 with SMTP id m20mr2608878agk.43.1279179020103; Thu, 
	15 Jul 2010 00:30:20 -0700 (PDT)
Received: by t10g2000yqg.googlegroups.com with HTTP; Thu, 15 Jul 2010 00:30:20 
	-0700 (PDT)
Date: Thu, 15 Jul 2010 00:30:20 -0700 (PDT)
In-Reply-To: <8149d4dd-b890-48a0-a9ee-0ed8eb3306f4@w30g2000yqw.googlegroups.com>
X-IP: 69.255.188.5
References: <8149d4dd-b890-48a0-a9ee-0ed8eb3306f4@w30g2000yqw.googlegroups.com>
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/5.0 (X11; U; Linux x86_64; en-US) AppleWebKit/534.3 
	(KHTML, like Gecko) Chrome/6.0.458.1 Safari/534.3,gzip(gfe)
Message-ID: <f22a1d3b-6754-43aa-9b69-06ef988c8943@t10g2000yqg.googlegroups.com>
Subject: Re: Thinking in Web Apps: Design Principles for Chrome Apps
From: Brandon Thomson <gra...@gmail.com>
To: Chromium Apps <chromium-a...@chromium.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

"The Chrome Web Store or the developer's own website will provide the
description and copy necessary to explain or sell the web app. That
is, the discoverability of the app happens via the marketplace and
traditional search channels. For example, once inside a music app, a
user should not see extraneous banners explaining the benefits of the
music app. The user has already chosen and installed the app, and as
such does not need the app sold to them again. Just immediately
present UI elements that help the user achieve their goal."

It sounds like you are suggesting any kind of traditional landing page
for the app should be bypassed when the user comes from the Chrome Web
Store. But often landing pages are fullscreen affairs with lots of
graphics, descriptions of features and benefits, etc. Will the store
interface (which will presumably have lots of onscreen content related
to the app store rather than the specific application) sell users as
effectively as a fullscreen landing page?

Just a rhetorical question...

Regards,
Brandon

On Jul 14, 9:11=A0am, Michael Mahemoff <mahem...@chromium.org> wrote:
> Hi All,
>
> In Google's Chrome Developer Relations, a common question we're asked
> right now is "How is Chrome App different from a website?". =A0User
> experience is one of the key differences we are anticipating, =A0and to
> that end, we recently articulated several design principles for Chrome
> Apps, in "Thinking in Web Apps", which you can find here:
>
> http://code.google.com/chrome/apps/articles/thinking_in_web_apps.html
>
> Summary:
> =A0 =A0 * Tight focus
> =A0 =A0 * Big screen
> =A0 =A0 * Rich experience
> =A0 =A0 * Beauty
> =A0 =A0 * Speed
>
> This is a work -in-progress. None of us will know for sure what makes
> a successful app until the store launches and people start voting with
> their feet (or mice). But for people making apps right now, it's
> useful to make some educated guesses. We value your feedback and would