When developing an app for Android or iOS, it seems mandatory to set up a connected app in your own org and use the key from it in the bootconfig.json file. This is all easily done when developing and testing on a single org, but what happens when I want to distribute the app on Google play/Appstore? Obviously the app should be usable by people on many different orgs, but without the connected app backing it, they will not be able to reach their data. How is this best handled?
As a developer, you only need to create the connected app once, in a Developer Edition. You publish your app, and it's good to go. You do not need to create a connected app configuration in any other org. Users from other orgs can log in via your app, without there being a corresponding connected app in their own org.
As per my understanding it works like this:
1) You create connected app in you dev org
2) Then you create Android app providing details for your connected app in bootconfig.json file
3) After testing you package your connected app on SFDC and install it on your test org
4) then you install your Android app on test device
5) When you first try to access your Android app it ask SFDC user name pass when your provide details of your test org which has your connected app installed it binds your device successfully with your test org and not dev org.