Skip to content

Improve Getting Started Experience #3516

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

Closed
8 tasks done
rosen-vladimirov opened this issue Apr 3, 2018 · 0 comments
Closed
8 tasks done

Improve Getting Started Experience #3516

rosen-vladimirov opened this issue Apr 3, 2018 · 0 comments
Assignees
Labels
Milestone

Comments

@rosen-vladimirov
Copy link
Contributor

rosen-vladimirov commented Apr 3, 2018

Improve Getting Started experience

A major problem when starting with NativeScript CLI is the setup of local environment. In many cases the setup is not straightforward, so the developers never see their NativeScript application running on device/emulator/simulator.

The major goal here is to try to give different options how to see the real application running on device.

Improvements

  • Do not check environment on post install of CLI. In case the environment is not setup correctly, this leads to confusion, especially when the developer is unable to setup it. The developer should focus on the application and technology itself, not on the local environment setup.
  • After CLI has been installed (on post install) inform the users for the options they have - to try local builds, cloud builds or to try the Playground.
  • When tns doctor is executed, print information for the correctly configured parts of the environment, not only of the incorrect ones.
  • When tns doctor is executed, suggest the users to setup cloud builds or local setup in case there are issues with the configuration.
  • When tns run [<platform>] command is executed, check the environment and in case there are issues with it, prompt the user to setup the local environment via setup scripts, to setup environment for cloud builds, to setup environment for both local and cloud builds and to configure the environment manually. In case setup scripts are chosen by the user, run the scripts and check the environment after that. In case everything is correct, continue with the command. In case there are still issues, suggest cloud setup or manual configuration.
  • Same as for tns run [<platform>] should be executed on all other commands, like build, prepare, etc.
  • Introduce tns setup and tns cloud setup commands that should be able to configure your environment.
  • Add analytics for the result of the setup scripts, so we can track what has not been setup correctly. This will allow us to fix the Setup scripts.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants