Insights From a Spring Boot Leisure Project for Everyday Developer Life
summary
Developer reverse engineers the Android app with APKLab reverse engineering to call the device's undocumented GraphQL API, then builds a Telegram bot + Spring Boot service that uploads images, scales them, and runs as a Docker image built with Buildpacks and pushed to DockerHub via GitHub Actions. Deployment auto-updates on a home NAS with Watchtower auto-updates. Emoji rendering fails in the container until fixed by adding Google emoji fonts after two nights of debugging. It works, attracts family users, and exposes spam and API breakage risks.
AI-written summary · about
chapters (12)
- 0:00Welcome
- 1:04Leisure project concept
- 3:32New device pain points
- 8:19Reverse engineering mobile app
- 11:56Telegram bot with Spring Boot
- 13:25Lightweight hosting choice
- 15:14Emoji font issues in Docker
- 17:22GitHub Actions pipeline
- 19:56User base expansion challenges
- 22:48API changes and testing
- 25:42Key lessons learned
- 27:05Why leisure projects matter
related talks
48mInsights From A Spring Boot Leisure Project for Everyday Developer Life
45mLinuxOnAndroid - Reviving a 10 year old Android project
17mDeploying Android AOSP at Scale
01h 27m"Bootiful" Applications with Spring Boot
54m10X Android Development
30mHow We Moved from Android Studio to Slack
01h 09mBootiful Spring Boot: A DOGumentary
37mPersonal Projects as a Laboratory: Four Freedoms an Android Engineer Gains