Success

Notes

Error

 
 
 
 
Budget

3,000 - 6,000

Posted on

2014-07-24 16:49:59.0

Buyer:

Koy***

This project has expired

Why don't you register anyway? We are sure that you will find many similar projects out of the thousands waiting for you!

Post similar project now

Description

DO NOT RESPOND WITH SALES PITCHES BUT A DRAFT OF THE FOLLOWING 5 ITEMS BASED ON YOUR UNDERSTANDING OF THE HIGH LEVEL BUSINESS REQUIREMENTS

 

1. Project Plan: If you are interested, please do take time to read and understand our high level business requirements and then submit a project plan with specific start and finish dates that delivers a working beta version of the Android Mobile App within 6 – 8 weeks from start. This is required for a demo to publishers in September.

 

Please include a draft of the following:

2. End to End Platform Functional Design across all incorporated external & internal cloud services and processes

3. End to End Media, Transaction, Identity Management and Configuration Database storage Design and Specification

+

Database schema and Metadata"

4. End to End Logical Architecture Design across all external and internal Cloud services, network

5. API Design and Specification

 

These 5 submissions will be used to review and select the Developers for this project.

 

Step 2:

This will be a videoconference over Lync or Skype

 

We will also plan to visit your development team in eastern Europe or Asia Pacific after the project is awarded and development has started.

 

This is a fixed cost project and we only pay for acceptable work output not time spent. –  Apologies but this is from lesson learnt dealing with fraudulent providers particularly from India.

 

We expect weekly progress report submitted using template we would provide. You will also be required to provide a visual walkthrough of completed work and demo over videoconference every Friday.

This platform is envisioned to deliver a managed cloud Media Services that encodes, store, and streams video and audio at scale through:

1. Browser Web Application (iTunes Desktop App as a Browser Web Application)

End User Content Portal

- Store (Responsive to Mobile, Tablet/iPad and Desktop views)

- My Library (allowing online consumption from anywhere)

- My Account (My Purchases, Settings, Profile, Social Ntework)

- My Wish List

- Redeem Voucher and Send Gift Vouchers/Media files, Setting Allowances for Children

-  My Alerts

- Recommended for you

- Search

 

The design should allow Publishers charge using these 3 options for their media assets:

User Account Types - Billing/Charging Model:

1. Rent or Buy and Download to My Library on Mobile App or consume via Brower Web App - My Library

2. Monthly/Quarterly Subscriptions

3. Free + Ad

 

- Flash must not be used for this project, Non negotiable mandatory requirement. For web use HTML 5 video players strictly and for the mobile Apps go for native App solutions as is appropriate.

 

2.  Android Mobile Media Streaming App (supporting Audio and Video media content type)

- Audio and Video Media types are to be supported. Audio Sermons and Video Sermons are to supported

- on demand streaming and download and play are required

- This App combines store, library and my account functionality.

 

Benchmark standard Apps:

 

- Please note any Development output must match the design, development and performance standards of the above Apps as a mandatory acceptance and escrow. Player design and implementation including bit rate, quality, buffering is a key quality acceptance criteria – If you cannot deliver at this level, don’t take the on the project or indicate clearly if it is design only you can delivered or just the development aspect.

1. Amazon Music App

2. Itunes Store and Music App

3. Deezer Apps

4. Rdio Apps,

5. Spotify

6. Hulu

7. Vevo

8. You Tube

 

- Flash must not be used for this project, Non negotiable mandatory requirement

 

3. IOS Mobile Media Streaming App (supporting Audio and Video media content type)

 

- Audio and Video Media types are to be supported. Audio Sermons and Video Sermons are to supported

- on demand streaming and download and play are required

- This App combines store, library and my account functionality.

 

Benchmark standard Apps:

 

- Please note any Development output must match the design, development and performance standards of the above Apps as a mandatory acceptance and escrow. Player design and implementation including bit rate, quality, buffering is a key quality acceptance criteria – If you cannot deliver at this level, don’t take the on the project or indicate clearly if it is design only you can delivered or just the development aspect.

1. Amazon Music App

2. Itunes Store and Music App

3. Deezer Apps

4. Rdio Apps,

5. Spotify

6. Hulu

7. Vevo

8. You Tube

 

- Flash must not be used for this project, Non negotiable mandatory requirement

 

The above will be developed as a Base version.

 

Custom versions (with different UI design) of the browser web App and Mobile Apps will be released for different Churches/Publishers (also know as content publishers).

 

There will be 2 Management Portals

 

4. Platform Administration Portal: This is for us to manage and support Publishers and End Users

 

 

5. Publisher Administration Portal: This is like the itunesconnect.com interface for media (audio, video, eBooks) ingestion,

Media Ingestion Dashboard

- Single Media + Metadata Upload workflow

- Bulk Media + Metadata Upload workflow

- API Bulk Media + Metadata Upload workflow

Media Catalogue Library Dashboard

- Metadata + Tag Edit workflow

 

6. End to End Media, Transaction, Identity Management and Configuration Database

- Proposal is required on the acceptable and viable No SQL or SQL Database tools and resources to apply in this project and which cloud provider to use. Considerations include the media encoding, ingestion, high availability, performance, speed, real time streaming, secure, DRM applications to audio, video and ebook media assets.

 

Minimum expectations are:

- Production Database storage across multiple containers and regions

- Real-time, self-replicating DR Database storage that can go live automatically

- Back Up storage with back up happening multiple times a day

- Pre-Production environment

- UAT environment

- Analytics Database

Application Servers must be separate from Database storage with API access.

 

- All portals must be https

- All customer data and transaction data must be encrypted in storage and during transmission

- Design for extreme security, speed and search capabilities are acceptance criteria

 

- End to End Media, Transaction, Identity Management and Configuration Database storage Design

- Specification

- Database schema and Metadata

- Logical cloud storage design and specification across Azure/AWS/Google Cloud

 

 

This will in particular specify how the media database catalogue will be stored and accessed across multiple cloud storage providers in different zones integrated to CDNs, with realtime self replicating DR, Backup, Pre-production and UAT storage.  

This includes specification for Security, Customer Data encryption for storage and during transmission, speed and performance across all geographies using CDN and auto scaling.

You will also be required to specify KPI and Benchmarks the platform, API, requests, read, write, cache, SSL will be delivered against at operating at different traffic levels.

You will also specify how real time and offline Analytics will be delivered and finally a Cost Profile for your design across different traffic levels over a period of time using cost from the cloud service providers must be presented.

 

Actors

This will be supplied after project plan and initial design is received.

 

 

 

Deliverable: Payment and Billing Integration

'- Single Payment API interface to integrate multiple Payment methods/processors (Braintree, Stripe, PayPal, Interswitch)

- Multiple currency management (Launch currencies: GBP - £, USD - $, Euro - €, Canadian Dollars, Naira - NGN, Ghana - Cedis)

 

User Charging Models and Account types:

1. Rent or Buy and Download to My Library on Mobile App or consume via Brower Web App - My Library

2. Monthly/Quarterly Subscriptions

3. Free + Ad

 

Charging Filtered by Channels. Channels are:

1. Publisher Domain for each country. Each country website should be logged as a separate channel

2. Android Sermon App

3. IOS Sermon App

 

Deliverable: Platform Administration Portal

 

Member Access Dashboard

Billing Resolution Dashboard

Publisher Onboarding Dashboard

Media Ingestion Dashboard

User Management Dashboard

Publisher Payout Dashboard

- Payout Ledger

- Payout settings

 

 

 

Android Sermons Application ( Audio Sermons and Video Sermons)

'Media Type:

- Audio

- Video

Charging Approach:

'- Charging model on Mobile Apps: Selling Price - Store commission (30%) - VAT - Payment Processing charge

- Charging model on Browser web applications: No store commissions

User Account Types - Billing/Charging Model:

1. Rent or Buy and Download to My Library on Mobile App or consume via Brower Web App - My Library

2. Monthly/Quarterly Subscriptions

3. Free + Ad

 

 

Development Approach and Principles:

 

Language and Tools:

- Node.JS

- Backbone.JS

- Java Script

- HTML 5

- No SQL

- SQL

- Open Source web frameworks

- JSON, Java Script, Node.JS APIs

 

Open source web frameworks Resources:

Resources

- Node.JS Back End UI: http://www.nczonline.net/blog/2013/10/07/node-js-and-the-new-web-front-end/

- https://github.com/spikebrehm/isomorphic-tutorial

- https://github.com/wycats/handlebars.js

- https://github.com/visionmedia/superagent

- https://github.com/visionmedia/express

- https://github.com/flatiron/director

- http://gruntjs.com/

- http://esprima.org/

- http://browserify.org/

- https://github.com/orta/ARAnalytics. ARAnalytics is a analytics abstraction library offering a sane API for tracking events and user data. It currently supports on iOS: TestFlight, Mixpanel, Localytics, Flurry, GoogleAnalytics, KISSmetrics, Crittercism, Crashlytics, Bugsnag, Countly, Helpshift, Tapstream, NewRelic, Amplitude, HockeyApp, ParseAnalytics, HeapAnalytics and Chartbeat. And for OS X: KISSmetrics and Mixpanel. It does this by using CocoaPods subspecs to let you decide which libraries you'd like to use. You are free to also use the official API for any provider too. Also, comes with an amazing DSL to clear up your methods.

- https://github.com/artsy/artsy-ruby-client

- https://github.com/intridea/grape

 

Development Management Tools:

- Google Drive (Paid Drive)

- GitHub

- Pivotal Tracker

 

External Services (PaaS):

- Twilio

- Encoding Services

- Azure

- AWS

- Google Cloud

- Parse

- Facebook

- MixPanel and Google Analytics

 

 

Development Approach:

- All portals must be https

- All customer data and transaction data must be encrypted in storage and during transmission

- OAUTH 2.0 Authentication is a minimum requirement.

- Flash must not be used for this project, Non negotiable mandatory requirement

'- MVC: client-side MVC (Model-View-Controller) or MVVM (Model-View-ViewModel) - Client - Server MVC

- API: The bulk of the application logic (views, templates, controllers, models, internationalization, etc.) lives in the client, and it talks to an API for data. The web pages on the site must render on the server instead of the client - Mandatory Acceptance criteria

- Server set up and Implementation: Node.JS is our primary reference but The server could be written in any language, such as Ruby, Python depending on justification and approval after review

- Web App

- Single Page App principle  meaning that the bulk of the code runs in the browser in order to support a more modern, interactive experience.

- Resources to use include but are not limited to: libraries like Backbone.js, Ember.js, and Angular.js

Mandatory Acceptance criteria

-Sserve fully-formed HTML from the server for performance and SEO, but we want the speed and flexibility of client-side application logic.“Isomorphic JavaScript” apps, which are JavaScript applications that can run both on the client-side and the server-side. is the goal here for the purpose of clarity.

- With Node.js, a fast, stable server-side JavaScript runtime, creat the appropriate abstractions, we can write our application logic such that it runs on both the server and the client

- Routing: We want a single set of routes that map URI patterns to route handlers. Our route handlers need to be able to access HTTP headers, cookies, and URI information, and specify redirects without directly accessing window.location (browser) or req and res (Node.js).

- Fetching and Persisting Data: We want to describe the resources needed to render a particular page or component independently from the fetching mechanism. The resource descriptor could be a simple URI pointing to a JSON endpoint, or for larger applications, it may be useful to encapsulate resources in models and collections and specify a model class and primary key, which at some point would get translated to a URI.

- View Rendering: Whether we choose to directly manipulate the DOM, stick with string-based HTML templating, or opt for a UI component library with a DOM abstraction, we need to be able to generate markup isomorphically. We should be able to render any view on either the server or the client, dependent on the needs of our application.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

End Deliverables