Location based Social service

Creation of a mobile and desktop based content provider similar to Orb ([[login to view URL]][1]). Project must work with 80% of currently used and upcoming cellphones. It must be carrier independent and be capable of accessing triangulation information from cell towers. The Desktop client will be web based login and allow for video, music, photo and tv uploads. The desktop cleint will use modern W3C web standards and interface with other web applications such as google maps, technorati and writely. The server backend will be the central depository for user profiles location data business data and advertising. It will provide this information to both desktop and mobile client. The backend is preferrably ruby on rails framework and SQL database. The intention is to allow users to move information from their desktop to their mobile client and vice versa. Additionally the desktop will have a friend of a friend social networking feature. The social networking feature will allow for users to send and recieve data from their mobile phone and see who is near by through various triangulation methods. ## Deliverables 1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables): a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment. b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request. 3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement). * * *This broadcast message was sent to all bidders on Tuesday Jul 18, 2006 1:23:17 PM: As there have been a few questions please read this over. I am interested to hear feedback on the request for proposal. Please do not bid if you are not able to complete the task. Sincerely, hugo Design Ideas The OurCloud system architecture consists of three main components: Mobile Client Desktop Client Server backend Mobile Client ________________________________________ The mobile client is a cellphone user interface for logging into the OurCloud system, retrieving location-based information, setting current schedule/plans/location, chatting with contacts, uploading/downloading media. - Restrictions - The major restrictions (or desires) of the mobile client are as follows: Operate on most (> 70%) of currently used and upcoming cellphones Be carrier independent Require no or small incurred usage fees due to SMS or web/data access * Access location information or ce ll-tower information provided by the cellphone - Implementation ??" There are several options for implementing a mobile client. Options include using the new Opera Application Platform, which does not provide cell-tower access, or a Python application, which won’t work on most cellphones currently used in the US. Both options may be used for a quick demonstration application, but will not work for long-term deployment. Due to the restriction of working on most mobile phones and access to cell-tower or location information, the implementation should probably be a Java mobile software application. Using the J2ME platform, an application may have full access to location information on the cellphone, cell-tower GSM data, and data interfaces. A J2ME application is a larger development effort. Desktop Client ________________________________________ The desktop client will provide a computer based interface to the OurCloud system. This will pr imarily be through a Web browser interface, but in the future may also include desktop applets and widgets. The desktop client will add an additional layer of interface richness and depth over the mobile client. The Desktop client will utilize modern W3C standards of web format, including XHTML, CSS, Javascript, RSS, as well as interfacing with other web applications like GoogleMaps, Flickr, [login to view URL], et al. Server backend ________________________________________ The server backend is the central repository for user profiles, location data, business data and advertising. It will provide these services to both desktop and mobile clients and should scale with increasing user base. In order to encourage users and free advertising, several aspects of the server backend will be made available via public API (Application Programming Interface), similar to Yahoo! data or Google Maps. Such features would included uploading/downloading cur rent user locations, obtaining location-based data, and business obtaining current viewing and click-through statistics. The server backend will be implemented using the powerful and sustainable Ruby on Rails framework and an SQL database. Work breakdown and outsouring options ________________________________________ The three major components of the OurCloud system must be designed and operate in tight-conjunction. However, each system itself may be independently developed, meeting design specifications. 1) Mobile client ??" it would be desirable for a program team to develop the mobile interface in the J2ME platform. A rapid prototype system can be created in the Opera Application Platform or Python for short-term development and demonstration. 2-3 mobile developers & designers. 2) Desktop client ??" the desktop client is currently in active development. It would be desirable to have a web-design and user interface consulting or team members. 1 des igner and/or human-factors/usability developer, 1 web developer, possible to also have 1-2 desktop application developers for additional clients 3) Server backend ??" the server backed has been prototyped and is in active development. The current system will be developed and used in the beta demonstration period. For the future, it would be desirable to find a large-scale server systems operators or maintainers to handle scalability and maintenance tasks. 2-3 system/database developers, 1 system administrator Features ??" initial • Feeds • Photos • Locations • Personal Page • FriendsOfFriends Income ??" initial • Advertising ??" adwords • Subscription to premium services Features ??" future • Music • Video • Pay via mobile ## Platform The system must be platform independent. It must also support all major web browsers