Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ability to preview NativeScript apps without any local setup #3813

Closed
DimitarTachev opened this issue Aug 10, 2018 · 0 comments

Comments

@DimitarTachev
Copy link
Contributor

commented Aug 10, 2018

Currently, in order to get started with NativeScript, you need to install the local iOS and Android requirements . We could reuse the NativeScript Playground approach and improve the getting started experience by previewing the apps on the NativeScript Preview app without any local setup.

We could achieve that by completing the tasks below:

  • Extract a common Preview App module from the NativeScript Playground.
  • Integrate the module in the Playground.
  • Create a new CLI command (tns preview) for previewing an app without having a local setup. Also, suggest a fallback to the new command when there are local setup errors on tns run.
  • Integrate the module in the CLI LiveSync process.
  • Handle native files changes (e.g. AndroidManifest.xml) by showing some warnings/errors.
  • Handle usage of custom plugins different from the ones in the Preview app.
  • Show QR codes in the terminal for downloading the required apps and previewing NativeScript apps.
  • Handle upload of bigger files and apps.
  • Setup a new pubnub app for the CLI.
  • [Optional] Handle the connected devices if needed for Sidekick.
  • Write unit tests
  • Use URL shortener for the links and QR Codes
  • Check the unit-test runner
  • Check cloud commands
  • Check Sidekick
  • Handle build with --bundle
  • Support platform-specific messaging in the preview app
  • Help for the new command
  • Compare the major versions between the local and preview app dependencies and show warnings (e.g. the Angular one)
  • Do not show warning for JS only plugins in case --bundle is passed.
  • Avoid different minimum supported App versions between the Playground and the CLI
  • Limit the app size
  • Check internet connection on preview
  • Add Analytics data
  • Handle the case when runtime version of preview app is different from local runtime version
  • (Idea) Handle the playground apps download with a single QR code navigating to a new Playground page.
  • (Should) Cache the instance id and the used devices, so users should not scan the QR code every time. Ensure the use-case is correctly described.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
CLI Team
  
Ready for Test
3 participants
You can’t perform that action at this time.