One developer builds this app, and the same one answers the mail. Write to [email protected] and you will get a real reply, usually within a couple of days.
You bank one shield for every seven consecutive days you satisfy a habit, up to three at a time. Miss a day and a shield is spent automatically, so the chain survives. The day is still recorded as missed in the history — a spent shield is shown in the shield ledger on the habit’s screen, so the log never lies about what happened.
No. Turn on Break mode and every habit is frozen for as long as you leave it on, at no cost in shields. Those days are recorded as frozen rather than missed, so a flu or a fortnight away never reads as failure. It is in Settings, under The chain.
miniHabits keeps a local copy for offline use and synchronizes the committed habit document through your private iCloud database. On another Apple device, sign in to the same iCloud account and miniHabits can restore and merge the synchronized copy.
Sign in to the intended miniHabits iCloud account, open the hard paywall and tap Restore Purchases. Apple and RevenueCat will look for an eligible annual or lifetime purchase. If it does not return, email me with the short account ID shown in Settings — never send an Apple password or receipt.
Signing out removes miniHabits data from that device while keeping the private iCloud copy for recovery. Delete account removes the app’s private CloudKit data and the local copies. Account deletion does not cancel an annual App Store subscription; manage that separately in your Apple Account.
No. A Health mode was planned for 1.0 and was removed before release, so miniHabits reads nothing from Health and asks for no Health permission. Track steps or workouts with a quantity habit and type the number, or use a timer habit and let the app time it.
Export is on the roadmap and is not in 1.0. If you need your log out of the app before then, email me and I will help you get it.
Email me with the habit name and roughly which days look wrong. Streaks are recalculated from the log every time they are read rather than stored as a counter, so a wrong number usually points at a real bug and I would like to know about it.
Email [email protected]. Tell me your iOS version and what you expected to happen, and I will take it from there.