← All work

Friendly Friday Hike (fridayhikes.com)

STATUS
CLIENT WORK: LIVE
TIMELINE
AUG 2026 – PRESENT
SCALE
30 members · 8 scheduled events
ROLE
Problem definition · Workflow design · Application development · Deployment · Client communication · Maintenance
ARCHITECTURE
Passwordless authentication over a managed backend, with scheduled reminder emails and admin controls driven by a settings toggle rather than a code change.
STACK
Lovable · Lovable Cloud (auth, database, email)

BUSINESS PROBLEM

A women's hiking group was coordinating monthly hikes, RSVPs, and attendance by hand across text threads and email.

WHAT I BUILT

A member-facing site with passwordless sign-in, a published season schedule, self-service RSVP that members can change, self-marked attendance history, and automated reminder emails. Admins control roster visibility from a settings toggle rather than needing a code change.

RESULT

Live with 30 registered members and the full season published for RSVP.

MY ROLE

  • Problem definition
  • Workflow design
  • Application development
  • Deployment
  • Client communication
  • Maintenance

HOW IT WORKS

  1. 01A member enters their email and receives a sign-in link. There is no password to store, reset, or forget.
  2. 02The published season schedule lists each hike with date, location, and details. A member sets their RSVP to one of three states and can change it at any time up until the hike.
  3. 03After a hike, members mark their own attendance, which builds a personal history without the organizer tracking it by hand.
  4. 04Reminder emails go out automatically ahead of each event.
  5. 05Organizers control whether the roster is visible to members from a settings toggle.

TECHNICAL IMPLEMENTATION

Built on Lovable with Lovable Cloud handling authentication, the database, and transactional email.

Row-level access rules scope member data so a member reads their own RSVP and attendance records, while organizer views are gated behind a role check rather than a client-side flag.

Roster privacy is a stored setting read at render time, so the client can change it without a deploy.

LIMITATIONS

  • Attendance is self-marked, so the history reflects what members report rather than a verified check-in.
  • Reminder email delivery depends on the email provider; a member using an aggressive spam filter can miss one.
  • The site is built for a single group. Supporting multiple chapters would require a real tenancy model.