I led the development of MyOfLink as founding engineer, building a full-scale SaaS platform designed to help creators and businesses manage their online presence through advanced link infrastructure, analytics, and monetization.
The goal was to go beyond traditional “link-in-bio” tools by creating a high-performance platform that improves engagement, tracks user behavior, and enables scalable monetization.
I architected and built the platform end-to-end using Next.js, TypeScript, and Tailwind CSS, leveraging server-side rendering and React Server Components to significantly improve performance. The result was a fast, responsive product achieving a 95–98+ Lighthouse score and noticeably reduced load times.
A core innovation was the deep-linking system. I engineered a solution to bypass in-app browser limitations on platforms like Instagram, Reddit, and TikTok using intelligent user-agent detection and platform-specific routing. This improved link conversion rates and overall user engagement by approximately 40 percent.
I also built a real-time analytics dashboard to give users actionable insights into their traffic and performance. This included click-through rates, conversion metrics, and geographic data, enabling more informed decision-making for creators and businesses.
On the monetization side, I implemented a full Stripe-based billing system with subscription tiers, usage-based pricing, and webhook-driven automation. The checkout experience was designed to be seamless, secure, and optimized for conversion.
The final product is a high-performance SaaS platform that combines advanced linking technology, real-time analytics, and scalable monetization into a single cohesive system.
This project highlights my ability to design and deliver complex SaaS products from the ground up, with a strong focus on performance, user experience, and real business outcomes.
The 404 was treated as a proper page rather than a fallback state.
The number is constructed as an architectural drawing. The 4 and the 0 are formed from walls at true thickness, with furniture laid out inside the resulting rooms and dimension strings running along both edges. It sits inside the same drafting system as the rest of the site rather than borrowing a display typeface.
The error message then repeats. Instead of a single dialog, identical windows cascade back across the canvas, each one carrying the same 404 notice. It reads as a system throwing an unresolved warning over and over, which is the exact behaviour Heron is built to prevent inside a model.
Error pages are never in the brief. They're a good measure of whether a team understood the product or just styled it.
Treating a 404 as an actual page instead of a dead end is such a good instinct, where did the architectural drawing idea come from, personal interest bleeding into the work?