Mobile Android application
Budget: $750 – $1,500 USD
SIMPLIFIED
1. Purpose
a. Background
i. V4A has developed a mass media platform to focus on the delivery of content to users in a garden walled, no data cost environment.
ii. The content is distributed by standalone web servers.
iii. The development of a linked mobile application has been identified as a key driver in expanding the:
1. User experience and user uptake.
b. System overview
i. The concept is to have a mobile Android application, built in 3 or more phases, to enable the user to download content from the V4A device, watch it at their own leisure, and then have the usage stats reported back into the V4a database when they next connect.
ii. Encryption of content files on the mobile devices will start at a basic level and will be enhanced over time.
iii. Static banners will be displayed in the app, and all content will have a precursor video.
iv. Existing marker structure to be replicated in in the video ad:
1. Static banner displayed with DTS.
2. Video played with DTS.
3. Content played with DTS.
4. Content 1 minute played with DTS.
5. Content played to end with DTS.
Specific requirements
It is envisaged that the development will take place in 3 or more phases with the first phases being developed with the future requirements in mind.
Phases 2, 3 and any subsequent phases might not stage consecutively, based on the business requirements they might be moved forward or backwards on the project timeline.
a. Phase 1
i. All the functionality as expressed or implied in this document, full scope will be supplied when an NDA is signed.
ii. Integration to and use of existing databases.
iii. Integration to and use of existing content folders.
iv. Encryption of content on to mobile device.
v. Encryption keys will have to be expired at predetermined intervals and associated files deleted from the mobile phone.
b. Phase 2
i. More user engagement preferences such as identifying favourites.
ii. Tracking of watched content and comparison against possible content to generate a “Recommended For You” page.
iii. Compilation of all watched content to generate a “Trending” page.
c. Phase 3
i. Enhanced encryption.
ii. Using recognised DRM standard.
iii. Content to be expired at various intervals and removed from mobile device.
Digital Rights Management (DRM)
Mobile digital rights management (mobile DRM) refers to technology that enables the secure distribution, promotion and sale of digital content for mobile devices. The OMA sees mobile DRM as an enabler of controlled consumption of digital content, enabling content providers to specify usage rights on such content.
The requirement of an effective, yet lightweight, DRM system is critical to the proper operation of the application.
SOW and RFQ inclusions
The response the RFQ must be submitted to the writer by close of business on Wednesday 28th July 2021.
a. All functionality as described in Phase 1 and that functionality that can reasonably be implied needs to be included in the RFQ response for Phase 1.
b. Any assumptions and/or specific exclusions must be stated.
c. Provision must be made in the RFQ response for the creation of a fully scoped Technical Specification for the mobile application, including all meeting, review and sign-off activities.
d. Responses and pricing for Phase 2 and Phase 3 must be included in the RFQ response:
i. Include the minimum requirements as specified above.
ii. Include recommendations on features and enhancements and budgetary pricing, this will enable the evaluation team to determine the long-term suitability of the responding organisation.
e. The RFQ must include a high-level work breakdown structure (WBS) and associated timelines.
f. The RFQ costing must be itemised to the level of the WBS as well as totalled to the phase and total project level.
g. Any payment terms, payment progressions and recurring costs should also be clearly indicated.
1. Purpose
a. Background
i. V4A has developed a mass media platform to focus on the delivery of content to users in a garden walled, no data cost environment.
ii. The content is distributed by standalone web servers.
iii. The development of a linked mobile application has been identified as a key driver in expanding the:
1. User experience and user uptake.
b. System overview
i. The concept is to have a mobile Android application, built in 3 or more phases, to enable the user to download content from the V4A device, watch it at their own leisure, and then have the usage stats reported back into the V4a database when they next connect.
ii. Encryption of content files on the mobile devices will start at a basic level and will be enhanced over time.
iii. Static banners will be displayed in the app, and all content will have a precursor video.
iv. Existing marker structure to be replicated in in the video ad:
1. Static banner displayed with DTS.
2. Video played with DTS.
3. Content played with DTS.
4. Content 1 minute played with DTS.
5. Content played to end with DTS.
Specific requirements
It is envisaged that the development will take place in 3 or more phases with the first phases being developed with the future requirements in mind.
Phases 2, 3 and any subsequent phases might not stage consecutively, based on the business requirements they might be moved forward or backwards on the project timeline.
a. Phase 1
i. All the functionality as expressed or implied in this document, full scope will be supplied when an NDA is signed.
ii. Integration to and use of existing databases.
iii. Integration to and use of existing content folders.
iv. Encryption of content on to mobile device.
v. Encryption keys will have to be expired at predetermined intervals and associated files deleted from the mobile phone.
b. Phase 2
i. More user engagement preferences such as identifying favourites.
ii. Tracking of watched content and comparison against possible content to generate a “Recommended For You” page.
iii. Compilation of all watched content to generate a “Trending” page.
c. Phase 3
i. Enhanced encryption.
ii. Using recognised DRM standard.
iii. Content to be expired at various intervals and removed from mobile device.
Digital Rights Management (DRM)
Mobile digital rights management (mobile DRM) refers to technology that enables the secure distribution, promotion and sale of digital content for mobile devices. The OMA sees mobile DRM as an enabler of controlled consumption of digital content, enabling content providers to specify usage rights on such content.
The requirement of an effective, yet lightweight, DRM system is critical to the proper operation of the application.
SOW and RFQ inclusions
The response the RFQ must be submitted to the writer by close of business on Wednesday 28th July 2021.
a. All functionality as described in Phase 1 and that functionality that can reasonably be implied needs to be included in the RFQ response for Phase 1.
b. Any assumptions and/or specific exclusions must be stated.
c. Provision must be made in the RFQ response for the creation of a fully scoped Technical Specification for the mobile application, including all meeting, review and sign-off activities.
d. Responses and pricing for Phase 2 and Phase 3 must be included in the RFQ response:
i. Include the minimum requirements as specified above.
ii. Include recommendations on features and enhancements and budgetary pricing, this will enable the evaluation team to determine the long-term suitability of the responding organisation.
e. The RFQ must include a high-level work breakdown structure (WBS) and associated timelines.
f. The RFQ costing must be itemised to the level of the WBS as well as totalled to the phase and total project level.
g. Any payment terms, payment progressions and recurring costs should also be clearly indicated.