Rabbits are one of the most misunderstood companion animals. The guidance their owners need — grooming intervals, diet ratios, enclosure hygiene, the behavior signals that hint at illness — is scattered across forums, vet pamphlets and long videos, in three different languages. Owners piece it together themselves, and things get missed.
Rabbit Care started as AppWiz’s attempt to fix that: one native Android companion that turns scattered rabbit knowledge into daily, per-rabbit guidance. This post walks through the decisions that shaped it.
Native Android, local-first storage
AppWiz went native on Android rather than cross-platform. The interface is mostly lists, detail screens and reminders — there was no framework-shaped problem to solve, and the audience skews toward mid-range and low-end devices where jank is felt immediately. Native widgets keep the app fast on hardware that punishes abstraction layers.
The bigger call was storage. Rabbit Care treats on-device storage as the primary database: care guidance ships as bundled content, the bunny profile lives only on the phone, and everything works with the network off. There is no loading spinner between an owner and a grooming checklist.
A content model that separates guides from plans
The content layer has exactly two types. Expert guides are evergreen articles — nutrition, grooming, behavior, health warning signs — written to be correct for years, not news. Care plans are the scheduled, personal layer computed per rabbit.
Keeping those separate kept the editing surface small and made plans computable: a guide never needs to know which rabbit is reading it, and a plan never hard-codes care knowledge, it only schedules it.
The care-plan engine: profile, reminders, plan
The engine is a three-step pipeline. First the owner describes their rabbit — breed, age, weight, living setup. Next, the engine maps those profile attributes onto care requirements: long-haired breeds get more frequent brushing schedules, outdoor setups get stricter hygiene checks, young rabbits get different health-watch items. Finally it generates a concrete plan of dated tasks and drives smart reminders from it.
When a profile changes, the plan regenerates. That one rule — profiles are the source of truth, plans are derived — eliminated the entire class of “stale schedule” bugs the design would otherwise have invited.
Privacy-first, and not as an afterthought
Profile data is encrypted on device with AES-256. There are no accounts, no analytics SDKs, and no server anywhere holding a bunny’s details — uninstalling the app removes every trace. That constraint shaped the architecture upstream: a sync-free design is simpler to build, simpler to test, and cheaper to run than a backend that would exist only to violate its own privacy promise.
Moderating community Q&A
The community section lets owners ask questions and share experience. Moderation combines a reported-content queue, keyword screening for medical red-flag terms — those threads get an automatic prompt to see a rabbit-savvy vet — and human review of anything flagged. The goal is a section that stays useful without turning into a substitute for professional care.
What shipping to Google Play taught AppWiz
Rabbit Care is live on Google Play with a growing community of rabbit owners. Three lessons stand out. Reminder-driven bursts beat feature depth: owners open the app because a task is due, not to browse. Offline-first was mentioned in reviews more than any single feature. And the privacy stance quietly built trust — “no account needed” is the kind of simplicity people recommend to friends.
Those lessons now flow both ways at the studio: into client engagements through the mobile application development practice, and into AppWiz’s second own product, the ad-free Bangla NewsPaper reader — the subject of the next post.