In the fast-paced world of continuous integration and deployment (CI/CD), managing sensitive information like API keys, tokens, and credentials—collectively known as secrets—is not just a best practice; it's a critical foundation for security and efficiency. GitHub Actions provides a robust framework for automating workflows, but a common friction point for many development teams, particularly tho
The Challenge of Scalable Secrets Management in GitHub Actions For development teams scaling beyond a handful of repositories, managing environment-specific variables and secrets in GitHub Actions can quickly become a significant bottleneck. The manual duplication of configurations across multiple repos, especially when dealing with distinct environments like development, staging, and production
The landscape of mobile development is shifting beneath our feet. For years, "Smart Apps" were simply thin clients for powerful cloud APIs. If you wanted to understand the sentiment of a sentence or find similar documents, you packaged a JSON request, sent it to a server, and waited for a response. But the era of the "Cloud-First" mandate is being challenged by a new priority: Privacy-Centric, Low
If you've spent any time doing Android development from the command line, you know the rhythm: adb devices, adb logcat, adb shell, repeat. It works, but it's friction — switching between windows, retyping device serials, manually grep-ing through logcat noise. padb is a Python-based terminal UI that wraps all of that into one interactive session. No GUI required, no Android Studio open in the back
I got tired of the same three-step content publish loop: write draft → open CMS → paste, format, re-paste, fight the rich-text editor, click publish. Repeat for every environment — staging, then production. For one article, fine. For a team publishing 20+ pieces a month? That workflow is a quiet tax on everyone's time. So I wired up a pipeline that cuts the loop entirely. You commit a .md file to
Originally published on rohitraj.tech UPI fraud hit ₹805 cr in India last year. Cloud APIs leak data. So I built ScamRakshak — fully on-device scam detection. 3-tier inference engine: Gemma 4 LLM — context-aware classification LiteRT — fast pattern model Regex fallback — when battery low Full architecture write-up: https://rohitraj.tech/en/notes/build-on-device-ai-scam-detector-android-gemma Read
After getting frustrated with news apps designed to keep me scrolling forever, I built Trace - an Android app that aggregates news from 100+ sources and uses AI to create 30-second summaries. The app is free, no ads, no subscription. Just news that respects your time. The Problem Every morning I'd open Google News or Twitter and 30 minutes would vanish. Not because I was learning anything useful,
User types "android" into your search box. That's 7 API calls if you wired it the way I did the first time. A few months later I shipped a pagination bug where every infinite-scroll fetch flashed a full-screen loader for half a second. And then there was the Settings screen that needed to refresh the Dashboard when the user changed theme — but Settings couldn't import Dashboard without a circular