Apr 15, 2019 to May 3, 2019
Mobile / Client work
React Native for an ambitious product team.
A brief React Native engagement for a startup building a graph-based AI application.
Mobile applications
React Native
Startup collaboration
THE TECHNOLOGY
React Native
MOBILE / CROSS-PLATFORM
My role
React Native developer
Client perspective
Upwork client, 5.0/5
Client rating 5.0/5, without written feedback.
Read the work history on Upwork · Checked Sep 20, 202601 / THE CONTEXT
The challenge.
The client was developing a mobile application at a startup working with graph-based AI.
02 / ENGAGEMENT FOCUS
Where the work focused.
The contract was for React Native mobile development. The public record contains a client rating and identifies the application context, while the detailed job description is private.
03 / THE ENGINEERING
Technology & trade-offs.
01
Interface
React Native
My engineering perspective: what each approach helps solve, and what needs care.
React Native: share logic with care for the device
React Native combines React’s component model with native platform capabilities. I separate reusable screen logic from behavior that depends on the device or operating system.
The trade-off: Shared code still needs platform-specific checks for navigation, permissions, and native integrations.
Request state: keep the user informed
A screen waiting for a remote result needs clear progress and a useful failure path. Redux is one example of a store for coordinating that behavior across screens.
The trade-off: Example option: a state library does not decide retry behavior or explain an error to the user.
Contract details and sources
Brief React Native engagement
Engagement brief based on the original job title and available description.- Contract period
- Apr 15, 2019 to May 3, 2019
- Upwork status
- Completed contract · Checked Sep 20, 2026
- Work delivery
- Delivery date not recorded.
- Product today
- Current availability not verified