gradle-recipes VS httptoolkit

That recipe is only adding hardcoded values as build config fields. If you look at https://github.com/android/gradle-recipes/blob/agp-7.0/Kotlin/addCustomResValueFromTask/app/build.gradle.kts for example they create a task which can be cached and runs only when actually needed (if the inputs change for example).

Here is an example of a tsk that can access APKs. It automatically depends on package task, so when you run it, it will be executed after APKs are created.

The new variant API allows for delegating more work from configuration to tasks though, including doing things like computing version code/name in tasks. See recipe here.

https://github.com/android/gradle-recipes/tree/agp-7.0 is kind of old, we're going to update it today.

And we'll be expanding our Gradle recipes too.

HTTP Toolkit, you will need to install one in your PC and another one in the emulator.

Maybe not exactly what you're looking for, but if you could side-load on windows this app should work. https://httptoolkit.com/

use https://httptoolkit.com/ but it's getting a bit off-topic :)

I run HTTP Toolkit (https://httptoolkit.com) which passed $2k a couple of years back. No longer a side project, as it's made enough money for me to work on it full time for a fair while now, but it certainly started that way, and it's still a one-man show (plus many wonderful open-source contributors).

I suspect that'll be a common theme in answers here though: if you have a side project making $2k a month, in most of the world that's enough for you to go full-time and try to take it further. If you can make $2k/month on something working only part-time, you can definitely make a lot more if you focus on it.

On your questions: HTTP Toolkit is a desktop app (plus a mobile app and other components for integrations) but it's an Electron app that effectively functions as a SaaS (with a freemium subscription model) that just happens to have a component that runs on your computer. And actually getting to $2k wasn't overnight at all - it took a couple of years of slow steady slog. A few inflection points that made a notable difference (releasing rewriting support & Android support particularly) but mostly it was a matter of "just keep pushing", trusting the trajectory would keep going, and steadily grinding upwards. It's great where it is now, but it's hard work - a solo business is not for the faint of heart!

you can use tools like https://httptoolkit.com/ to check the requests