Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Introduction

This wiki explains the design and implementation of pdf players for mobile devices..

KN-17 - Getting issue details... STATUS

Background:

As of now we are using a pdf player as part of the mobile application and it is working as expected , but we don’t have an independent pdf player for mobile devices to experience.

Problem Statement:

we don’t have an independent pdf player for mobile devices to experience.

Key design problems:

  • How to render the pdf player in new ionic app

  • How can we extend to add for another player

  • How to test with different sizes of contents

  • Where we need store this application code

  • How to handle portrait and landscape

  • How to distribute APK to tester/adapters

Design:

Application Flow:

App UI :

Solution:

  • We are using the ionic framework to render the player and its link.

  • using ionic version of 6.1.9 and node js version is 14 onwards

  • We can have players like pdf ,video and epub and we can implement different components each.

  • Need to create useful components, which are home , player list, content list, pdf players

  • The home component is the landing component and it should have button and its name Experience Players

  • In the players list component we can have the list of the players

  • In the content list component we can have hardcoded list contents as of now , based on player selected in player list component

  • The player component will load the player with selected content from the list.

  • The player component will be integrated with respected players and the pdf player will be integrated in the pdf player component and follow the steps.

  • We are handling landscape mode only , not supporting the portrait mode.

  • As of now we can have one individual repository to store code or we can get details of new repo and store code.

  • We can have an apk link in the microsite so that it will be accessible to testers and adopters.

Pros:

  • Its easy to implement

  • we can have different components for different players

Cons:

  • We are supporting only landscape mode , not supporting portrait mode

  • As of now we are rendering a contents list from hardcoded data.

  • No labels