Making Care Easier to Reach
Not every barrier looks like a locked door.
Sometimes the barrier is a placement description written in a language you cannot read. Sometimes it is an install button that fights the browser, a photo cropper whose controls disappear behind a phone’s safe area, or an unsubscribe link captured by the wrong part of a PWA.
Between the large offline release and the new collaboration work, Meo Mai Moi shipped a quieter sequence of improvements across v1.16 and v1.17. The common thread was reachability: making useful care information easier to install, understand, present, and trust.
Public Care Information Across Languages
Public pet profiles, helper profiles, and placement requests can now present translated content in the visitor’s supported language.
These are exactly the places where language has practical consequences. A placement description may explain an animal’s temperament or medical needs. A helper profile describes what support someone can offer. A pet profile can carry context that matters to a potential caretaker.
The translation system records source-language and translation metadata, creates translations in the background, and lets public pages refresh while work is still in progress. Administration tools make the source language explicit and provide visibility into how translation requests behave.
Machine-assisted translation is not the same as a human who understands every local expression and rescue context. We should not pretend otherwise. The purpose is to reduce the first barrier while keeping the original content and its provenance meaningful—not to declare every generated sentence perfect.
That tradeoff is worth making visible. Broader access helps, and sensitive details still deserve human attention.
Let the Browser Handle Installation
Meo Mai Moi is an installable PWA, but browsers and operating systems already have strong opinions about how installation should work.
v1.16 stopped trying to over-manage the install prompt on Chrome, Edge, and Android. The browser now owns the familiar installation flow, while iOS-specific guidance remains available where it is needed.
The app manifest gained a stable identity, richer descriptions, screenshots, categories, and shortcuts. The offline fallback page was refreshed, demo login was made more reliable around the service worker, and the Offline and Syncing indicators now lead directly to sync settings.
None of this makes a dramatic screenshot. It makes the app behave more like something the device understands and less like a website negotiating with it.
Photos Need Room for the Actual Animal
Fixed image crops are convenient until they remove an ear, a tail, or the detail someone was trying to document.
Pet photos now support freeform cropping with better output quality. The mobile dialog was corrected so its Cancel and Apply controls remain reachable above device safe areas. Cards handle image loading more cleanly, responsive media variants are delivered more efficiently, and full images have clearer loading states.
Media conversions are also generated sooner, which reduces the period where an uploaded image exists but its useful optimized forms do not.
This is visual polish with a practical purpose. A pet photo may be an avatar, but it can also help identify an animal, show a physical change, or make a placement request feel real.
Relationships Should Be Easier to Restore
Pet relationship management gained suggestions for known collaborators, shortcuts for re-sharing, and safer handling when an owner or member leaves.
These improvements acknowledge a normal fact of care: access changes. A person may help again after an earlier collaboration ended. A pet may move between households. Someone leaving should not leave stale data or an impossible ownership state behind.
The interface now does more to help people re-establish the right relationship without making them reconstruct it from scratch.
Notifications Must Respect the Exit
An email unsubscribe link is a small promise: when a person asks for fewer notifications, the application should listen.
The unsubscribe flow now returns to a proper in-app settings screen with confirmation instead of relying on the older broken page. Notification email layouts, greetings, action links, and footer copy were repaired. Birthday reminders now calculate the first birthday correctly, and the service worker allows unsubscribe requests to reach the server instead of swallowing them as application navigation.
Telegram relinking, startup connectivity detection, and media behavior also received reliability fixes through the v1.17 patches.
These are not engagement optimizations. A notification system should deliver useful information accurately and make leaving straightforward.
Reach Is More Than Availability
Software can be online and still be hard to reach.
It can speak the wrong language, install awkwardly, hide a button behind the edge of a screen, crop away the meaningful part of a picture, or hold onto a notification relationship after the user has tried to end it.
The work across v1.16 and v1.17 addressed those smaller distances. Some of it used new machinery; much of it corrected details that should simply behave.
Accessibility is often discussed as a special layer added near the end. We think it is closer to a recurring question:
Can the person who needs this information actually get to it, understand it, and act on it?
There is always more work behind that question. These releases move us a little closer.