September 10 - 12, 2013

Community App Store Architecture


Community App Store Architecture


Billions of downloads occur every year through native app stores. The paradigm is familiar and pervasive, but what about mobile and responsive web apps? And what about cases where the hosting organization wishes to tailor the app store to their own world view?

The Community App Store Architecture, including the USE (URI Sharing Environment) Protocol and associated software, provides a mechanism by which organizations may share information about apps they're willing to share or sell through a network of peers in an automated fashion, modeling real world peering and trust relationships. The motivating use case for this protocol is web app stores, such as powering a mobile dashboard of user-selected apps, but this model also fits other use cases beyond mobile like web portals and learning management systems.

During this session, learn about how UCLA, the IMS Global Learning Consortium and others are collaborating on a standards-based approach to this problem that will enable organizations to create their own app stores and configure peering relationships with others to provide a richness of offerings to their users.


Eric Bollens is the Lead Software Architect of the UCLA Office of Information Technology's Education and Collaboration Technologies Group. In this role, he builds frameworks and APIs used at UCLA, across the University of California and throughout the open-source community. He currently manages development of the WebBlocks Responsive Toolkit and Community App Store Architecture.

At UCLA and as an IT consultant and open-source developer, Eric has over ten years of experience building web applications and architectures ranging from front-end mobile and responsive tools to application frameworks and end-user software to network and routing protocols. Ultimately, Eric's passion lies around constructing technical solutions to meet core business needs. He is also an open-source advocate and a subscriber to the DevOps philosophy.




Technical Level


  • Frameworks of the Modern Web
  • Mobile Research and Learning Interoperability
  • Mobile Web App
  • Automation