Yevhen Stuzhuk - Personal Portfolio
I am a Senior Software Engineer
Application development
Installable and mobile-first experiences: Expo/React Native, progressive web apps, and structured client applications with releases and quality gates.
Beyond marketing pages, I build applications people use daily: structured state, predictable navigation, and builds that survive store review or long-lived installs.
Whether you need a companion app or a focused mobile experience, the goal is clear scope, incremental delivery, and code your team can extend.
Representative work
Recent deliveries include speaking-cards and digitalvcard—systems where application development skills (TypeScript, React Native, Expo, PWA, React, offline-friendly UX, testing, CI, app store-ready packaging) were applied end to end.
Those projects combined product UI, APIs, and operational concerns: roles, exports, integrations, and observability. The goal is always software your team can extend—not a one-off demo that collapses under real users.
Typical collaboration starts with a written brief: constraints, integrations, compliance, and what “done” means for the first release. We slice work into vertical milestones so you see progress every one to two weeks and can reprioritize without losing the thread.
After go-live we offer a short hypercare window: fix edge cases, tune performance, and transfer knowledge. Long-term support can stay with your in-house team or continue as a retainer—your choice.
We document decisions in plain language, keep staging environments aligned with production, and leave runbooks so your team is not blocked after handoff. If you already have designers or backend engineers, we plug into your rituals instead of inventing a parallel process.
We document decisions in plain language, keep staging environments aligned with production, and leave runbooks so your team is not blocked after handoff. If you already have designers or backend engineers, we plug into your rituals instead of inventing a parallel process.
We document decisions in plain language, keep staging environments aligned with production, and leave runbooks so your team is not blocked after handoff. If you already have designers or backend engineers, we plug into your rituals instead of inventing a parallel process.
We document decisions in plain language, keep staging environments aligned with production, and leave runbooks so your team is not blocked after handoff. If you already have designers or backend engineers, we plug into your rituals instead of inventing a parallel process.
We document decisions in plain language, keep staging environments aligned with production, and leave runbooks so your team is not blocked after handoff. If you already have designers or backend engineers, we plug into your rituals instead of inventing a parallel process.
We document decisions in plain language, keep staging environments aligned with production, and leave runbooks so your team is not blocked after handoff. If you already have designers or backend engineers, we plug into your rituals instead of inventing a parallel process.
FAQ
Tap a question to expand the answer.
Expo/React Native or PWA?
Expo/React Native when you need app-store distribution and native APIs; PWA when the browser should feel like the product surface.
Do you publish to App Store and Google Play?
I prepare store-ready builds, signing setup guidance, and release hygiene; store accounts stay under your brand.
Is offline mode supported?
Where it matters: cached reads, queued writes, and clear UX when connectivity returns—scoped to real user needs.
How do you handle testing and CI?
Pragmatic CI checks and tests on critical paths—not ceremony; enough to catch regressions before users do.
Can you extend an existing web product?
Yes—companion apps often share APIs and auth with the web backend rather than duplicating business logic.
