I couldn't believe it: was noodling around with Kotlin. Built a cute lil newbie quiz app. Thought it'd be even cuter to try and push it to Google Play Store, forgetting that we can't have nice (or at least, in this specific instance, simple) things. Bad people have been abusing the ability to push malicious apps onto Play Store while pretending to be other people, I guess? I dunno. But suffice it to say that it is not a walk in the park to just hurl an app at the world.
Seasoned kotlin devs, UX designers, avert your eyes.
BEYOND silly. But it's job was to give me a reason to sniff-test the whole "publishing an app" experience.
While I've worked on an android app before, it was via React Native and I was decidedly not part of any publishing/deployment shenaniganry. Hence my curiosity:
When I tell you that Google would've happily taken stool samples, on top of everything else. I had to fess up photographic ID, address, phone number AND money, lol. But the kicker, folks... the kicker ended up being the need for a whole privacy page for this dinky little app.
.apk; had to backtrack and build an
.aabto sate the Android gods.
The obvious choice would've been just to stick up a page on here. Nothing on here requires a privacy page tho. Still, I could've just quietly added one. Otoh, I was eventually gonna have other apps, and I wanted them all to be sandboxed somewhere away from NTM; to froth forth out of the ether and die back into it, based on my whims and ideation/experimentation rates. I mean I had already bought a domain for precisely that. It was just sitting there, in R53, bored.
S3 to the rescue! I mean, it's just a static page, right?!
Cloudfront with R53
Aliasrecord for my cloudfront distro.
Freebie ACM SSL cert
*.mydomain.tlddoes exactly what it says on the tin and does NOT, in fact, "cover everything". So natch, Cloudfront balked, complaining that I was trying to feed it certs for
*.mydomain.tldwhile asking it to explicitly serve
mydomain.tld. LOL . OK so a second cert, then, this time for
wwwsubdomain after all, cos (i) ideally noone even gets to these pages and (ii) I vaguely remember that R53 charges for subdomains / CNAME records? Otoh it seems I need to keep the CNAME recs used for the verification runs, as they're used when the certs renew. Oh well.
Look forward to using the sandbox domain more, for future experiments.