Hossein Gerami

About & Core Expertise

Mobile Engineering

I enjoy building React Native apps with TypeScript and aim for smooth, predictable experiences. I keep screens simple, move logic into reusable hooks/services. The goal is steady performance, clear code, and fewer surprises in production.

UI/UX: design systems, dark/light themes, accessible components, gesture-friendly navigation, thoughtful empty/error states.
Patterns: feature-based folders, container/presentational split, custom hooks for side-effects, "services" for API/storage, and a simple repository adapter when talking to multiple backends.
Performance: virtualized lists (react-window/react-virtualized), stable keys, image optimization, avoiding re-renders with memo/useCallback, code splitting, and profiling with React DevTools.
State & Data: React Query for server data, Redux/Zustand when global state is needed, normalized entities, optimistic updates, and offline cache for spotty networks.
Native & Sensors: Expo + custom modules when needed, Keychain/Secure Store, camera, BLE/Wi-Fi/UDP for IoT, background tasks where appropriate.
Quality: unit tests (Jest), simple component tests, crash reporting (Sentry), basic analytics to spot friction.

React NativeTypeScriptExpoEASReact QueryRedux/ZustandFlipperSentry

Frontend Engineering (React)

I build React frontends that are clear, fast, and accessible.

Styling: solid base in HTML5, CSS3, SCSS, and Bootstrap for quick, consistent layouts.
Performance: virtualized lists (react-window/react-virtualized), stable keys, image optimization, avoiding re-renders with memo/useCallback, code splitting, and profiling with React DevTools.
State & Data: React Query for server data, Redux/Zustand when global state is needed, normalized entities, optimistic updates, and offline cache for spotty networks.
Large forms: break into steps, validate with schemas, autosave drafts, and use React Hook Form to keep it fast.
Tooling: TypeScript, Next.js (React Router), ESLint & Prettier
Next.js rendering: choose the right mode: SSR (server-side render) for data that must be fresh, SSG (static) for mostly-static pages, and CSR (client) when it's highly interactive or user-specific.
Testing: Jest + React Testing Library for units/components

ReactTypeScriptNext.jsViteCSS/TailwindReact QueryRedux ToolkitJest/RTLCypress

Integrations & Data Flows

I've spent a lot of time connecting apps to other systems and making sure data moves smoothly and securely between them.

Patterns: feature-based folders, container/presentational split, custom hooks for side-effects, "services" for API/storage, and a simple repository adapter when talking to multiple backends.
Services: built event-driven flows on AWS (Lambda, SQS/SNS, API Gateway).
Security: handled logins, tokens, and sensitive data with care.
Sync: kept customer, invoice, and claim data in step across systems.
Vendors: worked with Xero, MYOB, Sage, Dynamics, HubSpot, and NDIS services.

Node.jsTypeScriptAWSGraphQLXeroMYOBDynamicsHubSpotNetsuite

Observability & Support

I care about making sure the systems I build are easy to watch, understand, and fix when something goes wrong.

Intake: talk through what was expected vs what happened, and capture the right details.
Reproduce: set up a simple example to confirm the issue and add tests so it stays fixed.
Fix: improve error messages, add safety nets, and make problems easier to track down.
Document: share guides and notes so the next person can solve things faster.