This page is intended to be a starting point of the design for the end-user downloads Apps website. In maemo.org there is maemo.org Downloads, which is a good example of what can be expected.
I'll give a list of available data and suggestions of what we can add. Let's try to find out what a MeeGo Apps website should show.
After we have created a clear list of requirements, we can ask the community for a design or design suggestions. The work ongoing at apps-beta is currently concentrating on getting the correct data from the community OBS and making sure everything is in place for community QA. The Apps website itself will be running on top of this data, but with a clear end-user oriented view on top of this.
The Apps website will also have an OCS api interface, so App installer/clients can use the same data as the Apps website.
Feel free to add points. Make sure you end the line with --~~~~, so it is clear who posted what.
We should probably come up with wireframe designs, based on the discussion.
The Apps front page will most likely be visited from either a MeeGo or a non-MeeGo device. When browsing to the site from a MeeGo device, we can probably detect what version of MeeGo and architecture it is running by looking at the browser string. If this is not possible, we should present a screen where one can select the target UX, architecture and version.
After this selection has been made, it will be stored in the current session so that the interface will only show the correct target.
The actual front page for the selected target should show a top list of featured, new, updated, most downloaded.
Should it can also give a list of available categories? --Xfade 11:29, 9 February 2011 (UTC)
This should show detailed info about the application including screenshots.
This should show a list of available categories.
Comment blocks should be designed to fit in the style of the website and show the appropriate info.