Skip to content

CoverID/sub-app-rules

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

17 Commits
 
 
 
 

Repository files navigation

Sub-App SuperApp

Registration

  1. applicationId: e.g. bundle identifier or some unique app id
  2. applicationName: Name of the app
  3. developmentType: Mobile or Web
  4. applicationType:

for Mobile development type

  • ReactNative if the app built as React-Native Library, user access the app inside SuperApp
  • Native if the app built with native framework or other framework than React-Native, SuperApp trigger to launch the app
  • SPA user access the app with system browser like a website *you need to handle authenticated method from SuperApp

for Web development type

  • React if the app built as React Library, user access the app inside SuperApp
  • SPA SuperApp trigger to open URL in a new tab *you need to handle authenticated method from SuperApp
  1. iOSDeeplinkUrl: deeplink url for ios app (for Native app)
  2. androidDeeplinkUrl: deeplink url for android app (for Native app)
  3. webUrl: web app url (for SPA app)

Publishing (React-Native Library or React Library)

  1. Request personal access token (PAT) for npm authentication (Azure Artifacts)
  2. Set up .npmrc (Azure Artifacts)
  3. Create CI/CD and publish to SuperApp's Azure Artifacts
  4. Request SuperApp to set up the instalation Library

For Application Type: SPA

  • Web App will be automatically linked
  • Mobile App should request SuperApp to set up the instalation link

How to Access JWT Token and Switch Between Sub-App? Read this Documentation

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published