← Back to portfolio

Visitor Engagement · Apr 2026 – Present

NewRedo / Love Exploring

Working full time as a full-stack software developer on Love Exploring, NewRedo's cross-platform visitor engagement platform for parks, heritage sites, and attractions, combining a Flutter mobile layer, Unity-powered AR, and content-backed systems for treasure hunts, quizzes, video trails, and other distributed location-based game experiences serving 20k+ users across Android and iOS.

Role

Full-time Full-stack Software Developer

Timeline

Apr 2026 – Present

Stack

Flutter, Unity AR, Android, iOS, Next.js, Strapi, CocoaPods

Impact

20k+ users · Unity AR reliability · Flutter delivery

Visit loveexploring.app Discuss mobile and Unity delivery

Official Product Screenshot

Love Exploring application screenshot showing a dinosaur AR experience inside the mobile product.
Official Love Exploring application screenshot used as the primary still image for this portfolio entry.

Opportunity

Love Exploring has to move visitors cleanly between Flutter app screens, Unity-backed AR content, and CMS-driven attraction data. My work focuses on the full stack, but especially on making the Unity AR and backend-integrated system handoffs more reliable across Android and iOS while keeping the release process clear enough for repeatable delivery at a 20k+ user scale across both stores.

Experience Video

Local product video from Love Exploring showing the visitor-facing experience running in the production app style.

Live Website Preview

Live embed of the production website. If your browser or the remote site blocks framing, use the live-site link above.

Flutter and Unity AR

  • Implemented cross-platform Flutter and Unity AR improvements for treasure-hunt flows across Android and iOS, including AR and non-AR routing, camera handoff, safe-area handling, screenshot sharing, and return-to-map behavior.
  • Reduced friction in the transition between Flutter screens and Unity scenes so visitor journeys felt more predictable on-device.
  • Handled platform-specific polish for modern device layouts and mobile interaction edge cases.

Backend and content integration

  • Supported alternate API field mappings so backend or content variations did not break mobile experiences.
  • Validated missing question and model data before runtime to avoid fragile treasure-hunt launches.
  • Made Unity model matching case-insensitive to reduce broken AR launches and runtime errors caused by inconsistent content payloads.

Release and platform work

Mobile targets

Updated release and platform configuration across Flutter, Android, iOS, and Unity, including manifest and build changes, CocoaPods and Xcode updates, and Unity project settings for newer mobile targets.

Website and CMS

Contributed to the companion Next.js and Strapi marketing site plus CMS setup, including backend dependency updates that improved content validation and full-stack consistency between web, mobile, and Unity-driven experiences.

Release documentation

Documented the end-to-end mobile change and release process covering QA, approvals, rollout, rollback, and app store release steps so future changes had a clearer operational path.

Contribution focus

Experience quality

I focused on the fragile points users actually feel, especially Flutter-to-Unity handoff, AR entry and exit, screen safety, camera handoff, and route recovery back into the main experience.

Platform integration

The work sat at the boundary between Flutter mobile code, the Unity runtime, and CMS or API content, so the goal was to make those layers tolerant of imperfect data, platform differences, and the distributed system constraints that show up across multiple venues and experiences.

Release enablement

Beyond the code changes, I left the release process in better shape by documenting the checks and rollout steps needed to ship safely on both stores.