Jurri

Enterprise teams were juggling four tools to handle what should have been one workflow: storage, multi-account email, shared credentials, and access control. Every context switch leaked productivity, and the tools didn't talk to each other.

One product, three surfaces (files, inbox, vault) sharing a common navigation, search, and auth model. RTK Query handled server state with aggressive cache invalidation so the UI never felt stale. I split the frontend into composable components and custom hooks that the team could remix for new screens — what started as my code became the team's library.

Component reuse cut new-feature build time noticeably across the team. Bundle optimization (code splitting + lazy loading) dropped initial load by ~40%. The shared surface meant users stopped tab-juggling.

• 01Architected a reusable React component + hooks library that became the team's default ship surface.
• 02Built drag-and-drop file uploads with multi-file progress and resumable behavior.
• 03Implemented the unified inbox aggregating multiple email accounts behind one UI.
• 04Performance-engineered the bundle — code splitting, lazy loading — for a ~40% first-load improvement.