Mastering Android's Permission Model: Lessons from MoodifySDKMastering Android's Permission Model: Lessons from MoodifySDK
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
Sam's avatar
Sam Ayinla
• May 1
Building MoodifySDK taught me something I didn't expect.
The hardest part wasn't the ad integration or the UI. It was getting the after-call screen to actually show up.
Android's permission model is strict, and on newer versions, launching an activity from a background service after a call ends isn't straightforward. The screen kept getting blocked silently. No crash, no error. Just… nothing.
Turned out the fix was a combination of WakeLock, the right intent flags, and handling HiOS-specific quirks on TECNO devices that don't behave like stock Android.
Once I cracked it, the SDK worked across devices. It's now live in a production app, aftercall overlay, AdMob mediation, caller info, countdown, the whole thing.
I licensed it instead of just delivering it. Still own the IP. That decision alone changed how I think about the work I build.
Android Developmentindiedevsdk
Post image
Back to feed
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started