The major problem with app manager is to come up with a software list, from all the sources, dealing with component dependencies. Nokia could have setup a service/servers to crunch all these information, as software installation does require an internet connection to download packages. Local app manager listing fetches delta data from this service (such as new apps, removed apps, updated apps). When you think about it, app dependencies are not device-based, so all these relationships can be crunched on server side. To the end users, we care about the applications that we can install, update or remove. During installation or update (the device is connected to the internet), the user pick the require application(s) from a combined list (presenting only apps and description previously cached, together with the delta info sent from the server). After an application is picked, the server then decide what packages are required, and then tell the device to fetch them and install them. The server would also store information about each device's installed application (based on IMEI or SN), also storing a list of nominated repositories. Conceptually, kinda like Opera Mobile, where millions are users are rendering the same webpage (such as BBC News)...why not render it on the server side?