Website W/ Facebook Features 24.06.08
We need someone to build a site with core facebook/linkedin functionalities on a Java platform using Spring and Hibernate. The database will need to be in My-SQL.
The site will provide platform level functionalities to include the following features (similar to facebook):
1. Registration. We anticipated capturing key user profiles and demographic information here. The registration process must include email validation.
2. Core login and security features. We will need the site to authenticate users as well as supporting ‘forget password’ feature.
3. Profile and privacy features. As a registered user, the site needs to allow the user to create his/her own profile page similar to facebook. On the profile page, the registered user can set the privacy level for information categories he/she wants to share with the public.
4. The wall feature. Once a user has setup his profile, he/she can post comments about himself or herself. At the same time, his/her friends can also comment on the profile. All comments posted on the profile page can be hidden by the owner of the profile. As with facebook, users can delete, hide and remove wall comments.
5. Networking/friends feature. The site must allow registered users to search for one another and allow users to “add as friends”. The “add to friends” functionality must also notify the recipients and allow them to confirm the friends connection just like facebook and linkedin. The site should provide networks group setting, as determined by the site admin, for users to join similar to facebook. The site also needs to provide users with ability to create custom groups to categorize their friends. This networking/friends feature must be accessible and extensible by additional applications.
6. Invitation features. The site must be able to look at a registered user’s email address books such as outlook, hotmail, yahoo, gmail, aol, etc and send out invitations to selected email addresses. The invitation should have a default invitation message that is editable by the user. This default message should be managed by the messaging component in section 7.
7. Message features. Within the site, each user must have a mailbox to receive messages from other uses including invitations. The users of the site can use the inbox feature to send each other private messages as if it is their email box. The message feature should also be extended such that applications of the site can leverage this platform functionality to send/receive messages. The message component should provide the framework for the user interface, send/receive features, inbox/read/unread/reply/delete for core platform features such as the wall, invitations, and also applications.
8. News feeds: each event generated by the user with the system should be captured as a feed. There should be a functionality to add categorizations to each type of feed. Each type of feed should have a privacy setting and adhere to the user default settings. The news feeds should be extended to all functionalities and applications of the site, whether for display or auditing/reporting purposes.
9. The site must able to be extended for “applications” add-ons such as in facebook. The applications must have access to all site platform features, such as messaging, wall comments, networks/groups, invitations, news feeds and adhere to site privacy settings.
Other considerations:
All code should be modular and logically organized. All code sections must contain comments and developer notes. All code modules will be reviewed and QA for adherence to best practices before continuing work. Page comps and style guide will be provided for some, if not most of the components described. All code/design must adhere to the page comps and style guide.
Data model will need to be designed. We have a conceptual design of he data model and can provide guidance.
We will need to own the source code upon completion of the project and release of escrow.
