A platform enabling brand-creator collaborations, trend tracking, and social media monetization for the creator economy.
Emmanuel Loveday, also known as freewayz.dev
Software EngineerBuilding thoughtful interfaces, products, and developer experiences.
Frontend engineer focused on building interfaces that feel simple, fast, and intentional, from product UI to internal developer tools, with an emphasis on performance, accessibility, and craft.

Things I’ve shipped
A mix of product UI, developer tooling, and interface experiments, each one solving a real, specific problem.
A developer platform for building, testing, deploying, and managing Soroban smart-contract workflows on Stellar.
A smart-account ecosystem for user-controlled onchain finance, scoped automation, and cross-chain visibility.
An AI memory product that turns saved social posts from Instagram, TikTok, and Facebook into source-linked insights.
Recent roles
Where I’ve actually worked, most recent first.
Leading product, strategy, and the cross-functional team behind Cygio, a platform for brand-creator collaborations, trend tracking, and social media monetization.
The only frontend engineer on SoroBuild, SocketFi, and PingLet, real products spanning smart-contract tooling, onchain wallet infrastructure, and an AI memory app, after converting from an internship on the same team.
Started with React and Next.js as an intern, converting to a full developer role after six months.
Contributed frontend features with React and Next.js during a four-month engagement in Nashville, Tennessee.
University-mandated industrial placement building frontend interfaces and analyzing real project requirements.
On GitHub
Recent articles
Long-form technical writing on real problems, not generic listicles.
What Actually Changes About Engineering Decisions When You're a Technical Co-Founder
As an employee, someone else absorbs the cost of a wrong technical call. As a co-founder, you do. That one shift changes almost every decision, and it took me a while to notice it was happening.
You Don't Need Redux: A Practical Decision Tree for React State
Most state management questions get answered with a library opinion before anyone asks where the state actually lives, how often it changes, and who reads it. Start there instead.
A Field Guide to Debugging Memory Leaks in React Apps
The page that gets slower the longer someone leaves it open is almost always the same four causes. Here's how to actually confirm it's a leak, find which one it is, and prove the fix worked.
Five areas, one way of working
Different surfaces, same standard: thoughtful defaults, clear states, and interfaces people don't have to think about.
User-facing UI that has to hold up under real use: loading states, empty states, error states, not just the happy path.
Design tokens, component libraries, and the conventions that keep a growing codebase legible for the next person.
Internal tooling and CLIs that make other engineers faster. Unglamorous work with outsized leverage.
Full products end to end: routing, data fetching, auth, and the deploy pipeline underneath all of it.
Small, deliberate interactions: the details that make software feel considered instead of assembled.
User-facing UI that has to hold up under real use: loading states, empty states, error states, not just the happy path.
The engineering approach
Not a list of technologies: the real writing behind how I approach each layer of a product.
Design systems, accessibility, and interaction design: the layer users actually feel.
Component architecture, state management, and frontend structure that scales past one person.
Rendering strategy, bundle size, and memory, treated as a feature, not an afterthought.
Turning a vague idea into a shipped product, and knowing what to leave out.