Lolo Patch Notes — July 4 to July 10, 2026

What shipped

• More personal invite and referral links: Lolo join links now do a better job showing who invited you and why the link matters before signup, with cleaner branded preview cards for people, plans, and Circles.
• Context-aware plan and Circle sharing: plan invites and Circle links now carry clearer copy and richer previews, so a link in iMessage, Telegram, X, or a group chat feels like an invitation from a real person instead of a generic signup wall.
• Contacts became a bigger Find People loop: after scanning contacts, Lolo can show people already on Lolo and make it easier to invite the rest by SMS with the user’s referral link attached.
• Contact invite lists got search and Remix: long contact lists are easier to filter, and the invite list can reshuffle suggestions so more people are reachable from the same flow.
• Smart Plans added ETA and on-the-way coordination: users can share an ETA/status into a plan, stop sharing it, and see a lightweight on-the-way arc in Lolo without trying to replace Apple or Google Maps for turn-by-turn navigation.
• Connect mode shipped on the map: users can spread nearby avatars, lasso-select several people, and turn that group into a Smart Plan. Two-finger map navigation, selection glow feedback, and iOS haptics make the interaction easier to control on mobile.
• Plan check-in actions landed: Smart Plan reminders now support quick Pulled up and On the way actions across the in-app notification surface and supported native push flows.
• Wave Back for nearby pings: nearby-friend/ping notifications now have a lightweight Wave Back path so you can quickly tell the pinger “I’m around too” without writing a full message.
• Movement prompts shipped to production support: movement-based prompts now use the simpler copy “Drop a ping on Lolo.” / “See who you know nearby.” and can create a city-level ping when tapped, within the product’s privacy and rate-limit guardrails.

In the product

What improved

• Notification polish: nearby-person cards gained clearer Wave, Message, Coordinate, and Locate actions; wave feedback was cleaned up; and plan reminders now use more direct “starting soon” copy.
• Notification reliability and settings: Settings now has a simpler Enable Notifications path, with native iOS behavior routed through the app’s settings handoff where appropriate.
• Nearby alerts now persist inside Lolo: nearby-person pings no longer disappear after the native push. New alerts are saved to the in-app Notifications sheet and route into the same Wave, Message, Coordinate, and Locate actions.
• Map layering and readability: Lolo map overlays were hardened so foreground Lolo actions, ETA/on-the-way arcs, and ping/profile surfaces stay readable above boundary and preview layers.
• Dense-map relevance work: mutual filters and an opt-in For You ranking path moved forward behind the scenes, part of the push to make Lolo feel more personal as more people, Circles, contacts, and events appear on the map.
• Phone and account safety: phone-auth and contact-discovery plumbing received behind-the-scenes hardening to reduce account-takeover and abuse paths while preserving the contact-matching growth loop.
• Mobile-native readiness: iOS 1.0.8 is live per the latest status, with Google login hardening, native push registration, contacts scan support, movement prompts, check-in actions, Wave Back categories, and notification-settings improvements in the release train.

Growth/community notes

• Referral and Circle links are becoming a core growth surface: Lolo is leaning into links that already know the person, plan, or community behind the invite, instead of treating every share as a cold generic signup.
• Contacts are now part of the compounding loop: the product direction is simple: help users find people they already know, then invite the rest of their real-world graph into Lolo.
• World/community activations are still active: current planning continues around Lolo as an IRL network for World users, including verified-human event concepts and community/campus/city activation ideas.
• World Selfie Check entered testing: the verification integration is built and being tested as an additional privacy-safe trust factor for Lolo profiles and future verified-human IRL access concepts. It is not presented here as a finished public rollout.
• VELVET remains the clearest token-community Circle example: the VELVET holder Circle supports the broader direction of turning onchain communities into real-world communities. No new VELVET-specific launch is claimed in this week’s shipped list.
• Micro-plan experiments are still in measurement mode: early public plan tests in high-density cities remain in progress; the team is watching reads, RSVPs, and pull-up confirmations before turning this into a bigger loop.

What’s next

• Real-iPhone QA for 1.0.8: confirm Google login, Settings notification enablement, movement prompt tap-to-ping behavior, long-press Pulled up / On the way / Wave Back actions, contacts scan, and the notification-sheet scroll fix.
• Make the map feel more personal: keep improving For You ranking, friend/contact/Circle/X context, mutuals, density handling, and manual filters so the map surfaces the user’s actual village within the larger network.
• Keep tightening invite loops: continue polishing referral links, Circle links, contact invites, plan links, and social previews so sharing Lolo feels native in group chats, DMs, and events.
• Measure notification conversion: the notification optimizer and timezone rotation need more data before deciding which messages, timings, and contexts deserve more volume.
• Build community-grade Circles: strengthen Circle creation, joining, filtering, event/Smart Plan integration, and org-facing credibility before pitching more communities and event partners.

Source notes

These notes were compiled from the Lolo agent brief, open-loop status updates, recent Hermes session history, and the last seven days of commits in the Lolo app repository. User-facing claims above are limited to changes with explicit source evidence. Items still needing device validation are labeled as QA or behind-the-scenes/in-progress rather than presented as fully verified user-facing launches.

Public-safe sources included recent work on referral/contact invite flows, Smart Plans ETA/check-in actions, Wave Back, movement prompts, map layering, notification polish, iOS 1.0.8 status, and community/Circle planning. Private operational details, credentials, and internal-only identifiers are intentionally omitted.