I got tired of apps trying to monetize my attention.
Notifications, ads, endless feeds — it never stops.
So I decided to build an Android app with zero backend.
I'm a Japanese developer, and English isn't my first language, so I used AI to help write this article.
How many productivity apps have you downloaded, only to be greeted by a mandatory registration screen, bloated interface, pop-up ads, or a constant push for a premium cloud subscription?
Something felt missing from every app I tried.
I wanted the simplicity of a paper notebook combined with the convenience of a smartphone — a tool where my thoughts and tasks stay private, on my own device, without constant distraction.
So I built ZEROLOG — a fully offline, minimalist daily planner for Android.
In this article, I’ll share:
The design philosophy
The tech stack
The challenges of building a 100% offline app
And how I passed Google Play’s 20-tester requirement
The Philosophy: "Analog-Inspired" Digital Minimalism
ZEROLOG is inspired by pen-and-paper planning.
No loading
No accounts
No tracking
No notifications
Just open the app, write your day, and move on.
The Tech Stack
React 19
Vite 7
Tailwind CSS v4
Capacitor 8
Why Capacitor?
Capacitor lets me build with React while still accessing native features like:
Haptics (vibration feedback)
Local filesystem
Native notifications
Building a 100% Offline App
- Local-Only Data Storage All data is stored on-device using Capacitor’s filesystem API. No server No sync No tracking State is managed in React and saved asynchronously.
- Backup Without Cloud Since there's no cloud, I built an export/import system. Users can: Export data as a .json file Save it anywhere (PC, Drive, etc.) Restore it anytime You fully own your data.
- Habit Tracking & Vision Simple habit tracking with visual consistency Long-term planning with yearly + 3-month goals No pressure. Just visibility.
- Haptics & Localization Subtle vibration when checking tasks Supports: English Japanese Spanish Monthly Overview A simple calendar view: Shows daily activity No clutter No over-engineering The Hard Part: Google Play Testing To publish, I had to pass: 20 testers 14 consecutive days As a solo developer, this was tough. What worked: Indie communities (Reddit, X, Discord) Test swaps Keeping the app simple (no signup = easy to test) Business Model One-time purchase: $1.99 No ads No subscriptions No data collection Wrap Up Not every app needs the cloud. ZEROLOG is: Fast Private Distraction-free If you're curious about offline-first apps or want a calmer planner, try it: 👉 https://play.google.com/store/apps/details?id=com.masajiworks.zerolog 💬 Have you built an offline-first app? Let me know in the comments!
Top comments (2)
The tester gate section resonates. I went through the same with Money Me - a personal finance planning app I shipped as a TWA rather than a full native build. The 12 testers / 14 consecutive days wall is harder to clear than building the app when you're starting from zero audience.
Your point about no signup reducing friction is exactly right. The fewer steps someone has to do to install and keep the app, the more likely they actually follow through. Which communities worked best for you in the end - mostly Reddit and Discord, or did X pull its weight too?
I was only able to successfully recruit and communicate with testers through X in the end.
I tried Reddit, but I didn’t really understand how it works and got banned pretty quickly, so I gave up 😅
I also joined some Discord channels for mutual testers, but unfortunately, I didn’t get any response for my app there.
Interestingly, my X account wasn’t even focused on app development — it was mostly about my daily life and hobbies.
However, by using a few relevant hashtags, I was able to attract testers successfully.
X worked surprisingly well for early traction.