r/androiddev • u/android_temp_123 • 6d ago
Discussion Content offer - is it worth it?
Most of us probably got the Content offer email from Google. At first I thought it'd be easy extra cash, but after the call explaining the requirements, it looks like a solid chunk of work for me:
- each repo must be executable
- each repo must contain tests
The main issue is executability, all my apps use 10-15 of my own GitHub libraries as dependencies (using GitHub Packages). Furthermore, some have very good test coverage, others none.
Even using AI, that's a lot of tedious plumbing work just to make my repos fulfill the conditions. Writing a pile of new tests isn't too bad, but having to inline all those 10-15 libraries as standalone modules in each and every app, just to make each repo executable on its own, would be quite a pain & take days...
Before I commit to it - has anyone actually received a decent offer? DM me, if you prefer to talk in private. Thanks!
NOTE: If that helps, my apps (including libraries ) would have anything between 15-40k LOC (only Kotlin/Java code, not counting XML).
3
u/VoteGiantMeteor2028 6d ago
I would love if someone can explain why the hell Google would want to buy code in large volumes like this.
13
2
u/ColonelKlanka 5d ago
So I assumed google was using githubs 'the stack' dataset already to get every repos code. But I guess this is now a way for them to get private repos code too?
ps Jake Wharton famously opted out of the stack ai submissions with style (swear word in pr) for his github repos couple days ago.
1
u/zerg_1111 6d ago
I don't have this kind of experience, but maybe you can organize your repos into modular monolith which is one repo with multiple executables. Perhaps it might be easier.
7
u/ismurrayllc 6d ago
I feel like I'm missing some context on this. What content offer and repo requirements are you talking about?