FaceMap DesignOverall Design notes and diagrams. Overview of interactions, processes, and data. FaceMap Overview
The FaceMap system consists of two main components: The FaceMap server, and the FaceMap clients. While closely related, each performs a specific task necessary to create the end-product that the user will see. FaceMap ServerThe FaceMap Server is responsible for the direct interaction with both the Facebook and Google APIs. In addition to pulling relevant user data from both services, it is responsible for parsing and formatting data in a way that allows Facebook data to be understood by Google Apps, and vice versa. Written in PHP, this server-side component is the backbone of the FaceMap webservice. The FaceMap Server also serves the FaceMap Client to the end-user, after all processing and parsing is complete. FaceMap ClientThe FaceMap Client is the final user interface as seen by end-users. It is responsible for displaying the data as processed by the FaceMap Server in a manner that is both useful and easy-to-use. Written in JavaScript, this component is the client-side component that will communicate directly with the FaceMap Server. There are multiple client displays, as shown in the diagram above. By implementing various design patterns, it is possible to visualize the same user-data in many different ways, determined by both user-interaction as well as the context in which it exists. - The Facebook Application UI representation is a simple, watered down version of the product. It provides only the most core minimal features, in a compact package. It is designed to fit within the context of a Facebook Profile, and therefore provides mostly Facebook-centric features.
- The FaceMap Web Interface is the fully-featured, independent application suite. It will provide the user with the complete feature set, including many Google Apps interactions. It will also provide many "view" customizations, allowing the user to display only the most relevant data to him/her.
|
Sign in to add a comment
