Meeting between Mark Hope and Karly Oykhman covering the current state of the Aiden wedding planning app: mobile layout fixes, a new admin dashboard, CI/CD pipeline, test coverage goals, and several UX improvements. The team agreed to shift focus from new features to stability.
Attendees: Mark Hope, Karly Oykhman
Source call: Weekly sync, 2026-03-27
The Aiden app has reached a stabilization milestone. Mobile layout issues are resolved, a comprehensive admin dashboard is live, and a CI/CD pipeline is now active. The team agreed to freeze new feature development in the short term and focus on reaching 80% test coverage and fixing remaining bugs before a V2 roadmap is pursued.
Action — Karly: Test the app on phone and iPad this weekend and send feedback to Mark.
A fully rebuilt backend control panel is now live. Features include:
| Section | Details |
|---|---|
| CMS | Blog post editor (with SEO fields), promo code management |
| Vendor Directory | Searchable, filterable by category, state, featured/active status |
| Subscribers | List view with search by name, active status, no-event filter |
| Analytics | Signup trends, weekly activity, onboarding funnel, feature adoption rates |
| Technical | Data/security status, cron job health, SMS/push notification config, AI feature monitoring, database table sizes |
| Account Lifecycle | Subscriber count, emails sent, waitlist |
The Subscribers tab was throwing a client-side exception due to a pagination error introduced when the 100-record limit was replaced with paginated results.
"I added pagination. So every hundred, it makes a new page. And when I added the pagination, it broke that." — Mark
Action — Mark: Fix the Subscribers tab pagination bug. (Fix was deployed during the call; verify it holds.)
Action — Mark: Add a trial vs. paid filter to the Subscribers/Analytics view.
A Continuous Integration / Continuous Deployment pipeline is now active.
Flow:
Local dev (Mark's machine)
→ Push to GitHub repository
→ Automated tests run (CI)
→ Deploy to Vercel (production)
| Layer | Tool |
|---|---|
| Code repository | GitHub |
| Production server | Vercel |
| Database | Supabase (separate server for resilience) |
| Testing / responsiveness | Playwright |
| Uptime monitoring | Separate uptime monitor (always-on) |
First-time users will be guided through the collapsed admin dashboard via a setup walkthrough. Not yet built — flagged for near-term implementation.
All "bride/groom" references replaced with "partners." A future enhancement could let users choose their preferred terminology during onboarding setup.
New date validation rules prevent illogical entries (e.g., rehearsal date after wedding date). If a key date changes, the system warns the user that dependent dates need to be updated.
Action — Karly: Test date integrity and warning flows; send feedback to Mark.
Current behavior generates a unique QR code per guest — useful for tracking but impractical for printed physical invites (each invite would need a different code).
Proposed solution: add an option for a single event-wide QR code that prompts guests to enter their name on arrival at the RSVP page.
Action — Mark: Evaluate QR code options (event-wide vs. per-guest) and propose an approach to Karly.
Mark set up a Karly-specific email address for the Aiden app. A contact@ alias was also created during the call.
Action — Karly: Accept the email invite, set a password, add the contact@ alias, and keep the inbox open for user inquiries.