Twitter API project

We are seeking an experienced designer/developer to create a website similar to Twitter by using the Twitter API. This website will closely replicate the experience of Twitter but allow for detailed tracking and insertion of custom content. The developer should have the following skills: • HTML • CSS • JavaScript (incl. Flowplayer) • PHP (incl. SQL PDO queries) • Twitter API User Experience Users will see a page similar to the Twitter log in page[image 1] but will not have the option to create an account. Users will log in with their Twitter username and password through Twitter API. Users will see their feed as it would normally appear on the Twitter mobile website[image 2]. Users will be able to scroll through their feed to read Tweet text, view Tweet images, and view Tweet videos. Tweets should appear similarly to their real Twitter counterparts. However, users will not be able to interact with their feed. Users cannot reply, like, or re-tweet any Tweet. Users cannot follow any external links (e.g. a URL for a news article) or internal links (e.g. hashtags, Twitter handles, menu items). Specifications This website will be hosted on a Linux-Nginx-Sql Server-PHP stack. Developer should use Visual Studio for source control and publish to our SFTP server for testing. This project should use only HTML, CSS, JavaScript, PHP, SQL Server, and the Twitter API. Normal Tweet content is determined by the user’s login and the Twitter API. Custom Tweet content and location in page is determined by PHP code that performs a lookup on a SQL Server database table. Custom Tweet content includes the following information: user image, username, user handle, user verification symbol, Tweet timestamp, Tweet text, Tweet image, Tweet video, number of likes, number of replies, number of retweets, and whether or not the Tweet is promoted.[image 3] Custom Tweets with videos should use Flowplayer’s JavaScript API. The video contents will be determined by a PHP lookup on a SQL Server database table. JavaScript should be used to track all interactions with the video(s), including any player events (e.g. play, pause, mute, volume change) or skip button being pressed. Videos may or may not have pre-roll advertisements attached. Whether or not the pre-roll is shown, and the content of the pre-roll, are determined by a PHP lookup on a SQL Server database table. Pre-roll advertisements may or may not be skippable. For videos that are skippable, the properties of the skip button should be determined by a PHP lookup on the SQL Server database. The properties include the text of the button, the time at which the button appears, and the time at which the button disappears. All user interactions should be logged with JavaScript and posted to a logging table on a SQL Server database using PHP. The format of the logging is as follows: user information is polled every second. The information recorded is the timestamp, which Tweets are in view, and what percentage of these Tweets are in view (e.g. if a user sees only the bottom third of a Tweet’s div, the value for this percentage is 33%). Additional logging is performed on an event basis rather than an interval basis. This additional logging includes any interactions with the video player, an identifier for what video is in the player, and the timestamp at which the interaction occurred. The style of the page and of every element of the Tweet box should be determined with robust CSS to allow for easy future style changes.