Storefront performance
Shopify Performance Stabilization
94% -> 84%
Checkout abandonment improved after JavaScript and render-path cleanup on a conversion-sensitive storefront.
Read Shopify ->
Justin Joseph / product engineer
I build interfaces that stay fast as products get more complex.
Best fit for commerce, SaaS, and interface-heavy products where UX, auth, performance, and delivery pressure all meet in the same surface.
The overlap is the useful part: critical frontend behavior, visible system state, and engineering decisions that still have to hold up when the product gets denser.
Proof From Shipped Work
The homepage should introduce the fit. The work should prove it.
Auth and platform cleanup
ACTOR Modernization
$7.8k -> $2.4k
Identity, tenancy, and session behavior were untangled while cloud cost dropped sharply on a large production system.
Read ACTOR ->Mobile product delivery
Abantu Loyalty App
Auth + rewards
Shipped mobile product work across rewards, messaging, and release flow without losing product clarity.
Read Abantu ->Where I Add Leverage
The work is usually somewhere between product polish and technical cleanup.
That overlap is where I tend to be most useful: when teams need sharper frontend execution without losing the systems discipline underneath it.
Performance-sensitive frontend
Commerce, landing pages, and logged-in flows where speed changes user behavior and weak JavaScript decisions become visible quickly.
Richer product interfaces
State-heavy surfaces that need hierarchy, restraint, and UI decisions that stay coherent as the product gets denser.
Auth and platform complexity
Products where roles, tenancy, lifecycle, and operational reality sit right underneath the interface.
Selected Work
Three useful angles on how I work.
Storefront performance
Shopify Performance Stabilization
Improved Shopify storefront performance to lower checkout abandonment.
Frontend proof through theme-level JavaScript discipline, render-path cleanup, and conversion accountability.
Abandoned checkout improved from approximately 94% to approximately 84%. Revenue scaled from approximately EUR 20k to approximately EUR 200k after performance unlock and increased ad spend.
Read case study ->
Systems depth behind the UI
ACTOR (Aladon) - Enterprise Platform Modernization
Modernized a legacy multi-tenant Blazor platform while reducing cloud cost and identity risk.
Useful when the frontend touches auth boundaries, role logic, tenancy, or high-risk product behavior.
Azure spend reduced from approximately $7,800/month to approximately $2,400/month. Removed SQLite tenant file management as a recurring source of setup and release failures.
Read case study ->
Mobile product delivery
Abantu Loyalty App
Delivered a mobile loyalty baseline covering auth, rewards, and campaign messaging.
Shows product judgment across auth, rewards, messaging, and repeatable shipping outside the browser tab.
Delivered a production-ready loyalty app baseline for ongoing product iteration. Established a repeatable mobile release workflow across the chosen frameworks.
Read case study ->
Why It Holds Up
The frontend gets better when the engineer understands the system behind it.
Performance under pressure
I have done frontend and platform work where speed and release decisions affected revenue or operational stability.
State and auth discipline
I treat permissions, tenancy, session behavior, and async edges as product concerns, not backend trivia.
Delivery maturity
The UI gets better when the engineer also understands incidents, deployment risk, environments, and cost.
Contact
If the role sits between product ambition and engineering complexity, it is probably a fit.
Especially relevant for teams building high-visibility marketing sites, commerce flows, auth-heavy SaaS, dashboards, or interface-heavy products that still need engineering restraint.