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

How to install Kivy launcher in an android phone #26

Open
marcelourquiza70 opened this issue Jan 5, 2022 · 2 comments
Open

How to install Kivy launcher in an android phone #26

marcelourquiza70 opened this issue Jan 5, 2022 · 2 comments

Comments

@marcelourquiza70
Copy link

marcelourquiza70 commented Jan 5, 2022

Following the instructions of the "how it works" section in github, leads to the kivy documentation page (https://kivy.org/docs/guide/packaging-android.html#packaging-your-application-for-the-kivy-launcher) which leads to downloading the kivy launcher at google play store. Since kivy launcher is no longer available at google play store, it doesn´t help. There is an option for people that doesn't have access to the google play store (http://kivy.org/#download.) but it leads to a blank page. So I suggest you include installation instructions, so that we can install kivy launcher using the files provided at github, if possible.
Maybe the http://kivy.org/#download link should point to the installation page (https://kivy.org/doc/stable/gettingstarted/installation.html) where we can find a link to the python-for-android kivy version. But it is not clear that installing python-for-android is the same as installing the kivy launcher. If it is, I suggest you make that clear somewhere in the instructions.

@chrysn
Copy link

chrysn commented Apr 13, 2023

As long as the APKs are only available through GitHub artifacts (described in #14), there's probably nothing easy to put into the docs yet.

It might be better to rephrase the docs for the time being without the launcher, or with just a reference that there is a WIP launcher.

@tshirtman
Copy link
Member

The CI could be configured to create releases when code is merged on main, or when a tag is created, and adding the artifact to the release, which would make it easier to link to, using the main branch would be fine if development happens in branches which gets merged when ready.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants