4 ms·
In my opinion, it's fine to just include your monetizing code in your repo. You can use config files or environment variables or something to hide private detai
by rococode 9y ago
In my opinion, it's fine to just include your monetizing code in your repo. You can use config files or environment variables or something to hide private details. As long as the ads you publish are fairly standard, I don't think anyone would mind - and it also leaves people who really don't like the ads the option to compile an ad-free version. If you really wanted to curry favor, you could even post a separate ad-free .apk release on your repo and just push a version with ads to official app stores.
- hooksfordays 9y agoThis is what I currently do with my app. The code is open source, it's free for anybody to build and install, the build steps are simply clone and build with Android Studio. I upload the debug .apk as a GitHub release with no valid keys (so no ads), but there are ads at the bottom of the screen on the play store version. It makes a little change every month and I've not had any complaints about the ads, except to offer a pay-to-remove option, which I mostly just haven't gotten around to yet.