This component supposed to serve two groups of people:
non-techie audience
developers
Non-techie audience
For the 1st group we need to make navigation as simple as possible. URLs should always reflect the MeeGo UX (user experience) context. For example getting a list of games for IVI should be as simple as going to: http://apps-beta.meego.com/IVI/Games . The users in this group should not be overwhelmed with information such as multiple variants or versions of a certain package, multiple repositories that a package resides etc.
Developers
For the 2nd group we just need to make sure that they can reach every individual rpm or deb package that has been imported to the system. Still having easy to remember and bookmarkable URLs is a must.
This component supposed to serve two groups of people:
Non-techie audience
For the 1st group we need to make navigation as simple as possible. URLs should always reflect the MeeGo UX (user experience) context. For example getting a list of games for IVI should be as simple as going to: http://apps-beta.meego.com/IVI/Games . The users in this group should not be overwhelmed with information such as multiple variants or versions of a certain package, multiple repositories that a package resides etc.
Developers
For the 2nd group we just need to make sure that they can reach every individual rpm or deb package that has been imported to the system. Still having easy to remember and bookmarkable URLs is a must.