ubuntu-appstore-developers team mailing list archive

[Dave Morley <davmor@xxxxxxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Okay a few questions I might be missing answers to:

1. The click search will be done by an online backend?

2. How do you search for useful .deb armhf apps if there is no apt db?

3. If there is going to be a apt db then why not add the click package
listing there too

4. For armhf apps and click apps will there be an entry added on
apps.ubuntu.com/cat which has primarily stored .debs to date.

5. Primary install will be carried out via dash what happens if an
install fails (currently you are presented with an alternate method
via your purchase email)

6. Documentation/Documentation/Documentation  we need some very good
docs taking a standard app process from start to finish, these need to
be easy enough to understand that anyone can use the sdk and build a
click app and publish it.  But also cover devs who are not using the
sdk to create and build from.
The dev needs to know what the review will entail.
What is an isn't acceptable in a package. (preferably added to a tos,
as well a link in the application upload page)
Where they can get help for design guidlines.
How they can add qa steps (if the app doesn't work for a user run
app-test to confirm if it does work, it might be that the user is
using it wrong).

I know a lot of this is possibly already in the works but I thought I
would ask about it incase there was anything missed or I'm
misunderstanding.
- -- 
You make it, I'll break it!

I love my job :)
http://www.ubuntu.com
http://www.canonical.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iEYEARECAAYFAlHRrykACgkQT5xqyT+h3Og1WgCgv8ftwIQ4vhGjgKi+47Zd5/IN
3iYAnjjyKH9eozhgnfZGu1BkoUaBfl7d
=dm8j
-----END PGP SIGNATURE-----