Care Is Shared Work
A pet may have one profile in an app, but care rarely belongs to one person.
There may be a family sharing daily responsibilities, a rescuer coordinating with a foster, friends covering food and clinic visits, or several people trying to remember who paid for what. The animal experiences one continuous life. The humans often experience scattered messages, partial records, and a surprising number of receipts.
Meo Mai Moi v1.18 is a large step toward treating care as the shared work it already is.
Groups Give Care a Place
Groups create a shared workspace where carers can organize pets and collaborate with clearer membership and roles.
Before groups, collaboration mostly grew outward from an individual pet. That works for simple sharing, but it becomes awkward when the same people care for several animals or need a stable place for their shared work.
A group makes that relationship explicit. Members can see the pets relevant to the group, move between them more naturally, and manage the shared space without pretending every collaboration is an isolated invitation.
This is not a social feature added to create activity. It is practical structure for care that is already happening.
Shared Money Without Becoming a Payment Platform
Food, medicine, vaccinations, transport, tests, and emergency treatment all cost money. Those expenses do not become less real because discussing them is uncomfortable.
The new finance workspace introduces shared pet-care ledgers. Carers can organize accounts and categories, record income and expenses, associate pets with a ledger, invite members, attach receipts, and link relevant health expenses to medical records.
Meo Mai Moi is not processing payments or trying to become a financial institution. The goal is more modest: preserve a trustworthy shared record of care money so people do not have to reconstruct it later from chat history and memory.
Financial records also require stricter boundaries than a casual note. v1.18 hardened ledger membership, pet assignment, transaction updates, deletion rules, and cross-ledger authorization. Totals and access should remain correct even when a group changes over time.
One Invitation Model
Sharing had grown several different doors. Pet relationships used one invitation path while newer resources needed their own collaboration flows.
v1.18 replaces the narrower relationship invitation with a unified resource invitation model. The receiving experience is clearer, invitation lifecycles are more consistent, and the same underlying rules can support pets, groups, ledgers, and future shared resources without disguising what is being offered.
This work also centralized pet access rules. Ownership, membership, health-record permissions, and removal behavior now have a more consistent authority path instead of accumulating slightly different answers in different features.
Consistency is not merely an engineering preference here. When access concerns an animal’s history or another person’s participation, surprising behavior damages trust.
Messaging That Behaves Like Messaging
The messaging interface was rebuilt around a more dependable conversation layout, including better scrolling, chat bubbles, attachment presentation, and live delivery behavior.
This sounds smaller than groups or finance, but collaboration fails quickly when messages arrive unreliably or the interface makes an ongoing conversation difficult to follow. Placement and handover work already depends on messaging; shared care makes that foundation more important.
We also expanded automated coverage across groups, finance, placement, messaging, notifications, and profile flows. A collaboration feature is not finished when the happy path looks good. Leaving, removing access, changing membership, handling an expired invitation, or editing a shared transaction are part of the feature too.
More Consistent, Including When the Network Is Not
The release standardizes more page layouts and shared UI components across the app. Finance navigation and transaction lists received focused polish, responsive media delivery became more efficient, and pet selection works more clearly across the new surfaces.
Offline fallback and mutation recovery also became more explicit. Not every collaborative action can safely happen without the server: membership, permissions, and shared financial state need current authority. The app should say that clearly, preserve recoverable work where possible, and help the user understand what needs attention when the connection returns.
That is the same principle behind our earlier offline work: resilience should not invent a private version of shared reality.
A Step Toward Google Play
v1.18 also adds an Android Trusted Web Activity wrapper and the release groundwork needed for Google Play.
This is packaging, not a separate Android rewrite. Meo Mai Moi remains the same web application and PWA, with an Android surface that can make installation and device integration more familiar. Store availability still deserves its own announcement when the distribution work is complete; this release establishes the foundation.
From Records to Coordination
Meo Mai Moi began with a personal problem: keeping the records for nine cats in one place.
Good records still matter. But the next problem appears as soon as care crosses a human boundary. Who has access? Who is responsible? What changed? Which pet was this expense for? Has the other person seen the invitation or message?
Groups, ledgers, invitations, and messaging do not replace human trust. They give it somewhere clearer to operate.
Care is personal.
It is also shared work.