Custom Mobile-Friendly Web-Based PDF Viewer
Budget / Salary₹1,000–1,500
TypeFreelance project
LocationRemote
Posted2 hours ago
PDF Viewer for Mobile Web Browser – Story Play
I need a custom web-based PDF viewer optimized for mobile browsers. The viewer will be used as part of a story-play/interactive story experience, so it should have a clean, attractive, user-friendly interface rather than simply displaying a standard PDF viewer.
Main Requirements
• Develop/integrate a PDF viewer that works reliably in mobile web browsers.
• The PDF will be used to present a story, with users moving through the story page by page.
• Provide clearly visible Previous / Next navigation controls.
• Include a suitable page indicator, such as Current Page / Total Pages.
• The UI should be attractive and suitable for a children's/story-reading experience.
• The viewer must be fully responsive across different mobile screen sizes and orientations.
• The viewer interface must be customizable through a separate CSS file, allowing colors, fonts, buttons, spacing, backgrounds, sizes, etc. to be changed without modifying the core viewer functionality.
• Avoid the browser's default PDF viewer UI where possible; the goal is to have a custom story-player interface.
PDF Protection
• The PDF should be displayed inside the webpage rather than provided as a normal downloadable file.
• Disable/hide standard Download, Save, Print, Open in New Tab, or similar controls wherever technically possible.
• Prevent direct access to the original PDF URL where reasonably possible.
• I understand that once content is delivered to a user's browser, 100% prevention of copying/extraction cannot be guaranteed. The goal is to provide the strongest practical protection against normal user downloading or saving.
Mobile & Android WebView Testing
The developer must thoroughly test the viewer across different mobile devices, operating systems, browsers, and screen sizes.
Testing should include, where available:
• Android phones with different screen sizes/resolutions
• iPhone/iOS devices
• Android Chrome
• iOS Safari
• Other relevant mobile browsers
• Android WebView — the viewer must be tested inside an Android WebView environment, not only in Chrome
• Different Android versions and device configurations
• Portrait and landscape orientations
The developer must specifically verify that PDF rendering, Previous/Next navigation, scrolling/page transitions, UI responsiveness, touch interaction, and PDF protection behavior work correctly inside Android WebView.
A test report must be submitted containing:
• Device/model
• Operating system/version
• Browser/WebView version
• Screen size/resolution
• Orientation
• PDF rendering result
• Previous/Next navigation result
• UI/responsiveness result
• Touch/interaction result
• Download/save protection test
• Android WebView test result
• Any issues found
• Final pass/fail result
The viewer must be tested across a sufficiently diverse range of devices rather than being tested on only one phone.
Source Code & Customization
The complete source code must be provided at project completion. The implementation should be structured cleanly, with the visual styling separated into a CSS file so the story-player appearance can be customized easily in the future.
Any third-party libraries/components used must be clearly identified and must have licenses compatible with the intended commercial use.
Intellectual Property & Commercial Rights
At the end of the project, the developer must sign the required IP Assignment / Commercial Rights Transfer agreement.
All custom source code, development work, UI implementation, and other project deliverables must be transferred to me with the rights necessary for commercial use, modification, distribution, and resale.
The project will be considered complete only after:
1. The PDF story viewer is fully implemented.
2. Previous/Next story navigation and the required UI are working.
3. CSS-based customization is implemented.
4. Testing on mobile browsers and Android WebView is completed.
5. The complete test report is submitted.
6. Complete source code and other agreed deliverables are provided.
7. The required IP/commercial-rights documentation is signed.
NOTE:Please donot bid if the actual bid price out of range .Only bid if really want to work at the budget specified.
I need a custom web-based PDF viewer optimized for mobile browsers. The viewer will be used as part of a story-play/interactive story experience, so it should have a clean, attractive, user-friendly interface rather than simply displaying a standard PDF viewer.
Main Requirements
• Develop/integrate a PDF viewer that works reliably in mobile web browsers.
• The PDF will be used to present a story, with users moving through the story page by page.
• Provide clearly visible Previous / Next navigation controls.
• Include a suitable page indicator, such as Current Page / Total Pages.
• The UI should be attractive and suitable for a children's/story-reading experience.
• The viewer must be fully responsive across different mobile screen sizes and orientations.
• The viewer interface must be customizable through a separate CSS file, allowing colors, fonts, buttons, spacing, backgrounds, sizes, etc. to be changed without modifying the core viewer functionality.
• Avoid the browser's default PDF viewer UI where possible; the goal is to have a custom story-player interface.
PDF Protection
• The PDF should be displayed inside the webpage rather than provided as a normal downloadable file.
• Disable/hide standard Download, Save, Print, Open in New Tab, or similar controls wherever technically possible.
• Prevent direct access to the original PDF URL where reasonably possible.
• I understand that once content is delivered to a user's browser, 100% prevention of copying/extraction cannot be guaranteed. The goal is to provide the strongest practical protection against normal user downloading or saving.
Mobile & Android WebView Testing
The developer must thoroughly test the viewer across different mobile devices, operating systems, browsers, and screen sizes.
Testing should include, where available:
• Android phones with different screen sizes/resolutions
• iPhone/iOS devices
• Android Chrome
• iOS Safari
• Other relevant mobile browsers
• Android WebView — the viewer must be tested inside an Android WebView environment, not only in Chrome
• Different Android versions and device configurations
• Portrait and landscape orientations
The developer must specifically verify that PDF rendering, Previous/Next navigation, scrolling/page transitions, UI responsiveness, touch interaction, and PDF protection behavior work correctly inside Android WebView.
A test report must be submitted containing:
• Device/model
• Operating system/version
• Browser/WebView version
• Screen size/resolution
• Orientation
• PDF rendering result
• Previous/Next navigation result
• UI/responsiveness result
• Touch/interaction result
• Download/save protection test
• Android WebView test result
• Any issues found
• Final pass/fail result
The viewer must be tested across a sufficiently diverse range of devices rather than being tested on only one phone.
Source Code & Customization
The complete source code must be provided at project completion. The implementation should be structured cleanly, with the visual styling separated into a CSS file so the story-player appearance can be customized easily in the future.
Any third-party libraries/components used must be clearly identified and must have licenses compatible with the intended commercial use.
Intellectual Property & Commercial Rights
At the end of the project, the developer must sign the required IP Assignment / Commercial Rights Transfer agreement.
All custom source code, development work, UI implementation, and other project deliverables must be transferred to me with the rights necessary for commercial use, modification, distribution, and resale.
The project will be considered complete only after:
1. The PDF story viewer is fully implemented.
2. Previous/Next story navigation and the required UI are working.
3. CSS-based customization is implemented.
4. Testing on mobile browsers and Android WebView is completed.
5. The complete test report is submitted.
6. Complete source code and other agreed deliverables are provided.
7. The required IP/commercial-rights documentation is signed.
NOTE:Please donot bid if the actual bid price out of range .Only bid if really want to work at the budget specified.
Apply on Freelancer →
Project sourced from Freelancer.com. Applications happen directly on the original platform — we never collect your data.