iOS and Android
Feature parity between the iPhone and Android apps, the shared backend, and the few known differences.
Your clients may be on an iPhone or an Android phone. For your purposes, treat them as the same app.
Same features, same backend
The Android app is built as a deliberate one-to-one copy of the iPhone app. Both talk to the same Pippa backend for syncing, so a client's meals, plan, messages, chat history, and check-ins all flow to your dashboard the same way regardless of device.
The core experience matches on both: meal logging (photo, describe-it, and skip), the delayed post-meal check-in with fullness, feelings, urges, the clinician-gated purge follow-up, coping skills, and your custom questions, nutrition visibility (the protein and fiber bars or suggestion line), the AI chat with its disclosure, crisis tiers, and coping-skill chips, the pet and opaque-coin economy with soft streaks, the Play hub and Calm Corner, exchange and plate meal-plan targets, meal-plan backlogging, patient-to-clinician messaging, and the private local-only journal. The ED-safety rules (no patient-facing calories, skips never punished, support-only notifications) hold on both.
Shared logic, verified
The two apps share the same canonical rules for the details that matter clinically. For example, both attribute a log to the nearest enabled meal slot within a 90-minute window, both cap messages at 2000 characters with the same wording, and both score assigned questionnaires identically on the server. These were audited for parity so a signal means the same thing no matter which phone your client uses.
Known differences
A small number of platform-level differences exist, and none of them change the clinical picture:
- Push notifications on Android are still being wired up. Scheduled local reminders (meal times, mood, goodnight, the post-meal check-in) work, but server-initiated push may lag on Android.
- Sign-in with Google and Apple on Android is being finished; email sign-in works on both.
- Minor UI-only insight cards (such as some mood-calendar visualizations) landed on iOS first and are catching up on Android.
You do not need to ask which phone a client has to support them. The workflow, the copy you would reference, and the data you see are the same. If something looks missing for a specific Android client, a push or third-party-login gap is the most likely cause, not a difference in the recovery features themselves.