Okike SolutionsDigital product studio
Okike Solutions · Studio journal

Field notes from shipped work.

Practical accounts of the systems, decisions, and lessons behind products we build and operate.

Shipped system · Observability flow

@packages/observability
React Native
Convex
Node.js

wide event

One shared schema

request · service · operation · duration · outcome

destination

Axiom

Queryable logs across every runtime

≈400lines
3runtimes
<10mreported resolution
Architecture diagram showing React Native, Convex, and Node.js sending a shared wide-event schema to Axiom.
Field note · Engineering systems
Featured field noteReact Native · Convex · Node.js

Building Unified Observability for a React Native + Node.js + Convex Monorepo

How we built @packages/observability to get consistent logging and tracing across our Expo app, Convex backend, and Node.js scripts. Plus the CORS gotcha that almost broke it.

Read the field note

Inside the field note

Results reported in the article

≈400 lines

One shared TypeScript package

3 runtimes

React Native · Convex · Node.js

<10 minutes

Issue resolution, down from ~40

Editorial scope

What belongs here.

We publish when shipped work produces something specific enough to be useful—not to fill a content calendar.

01

Product operations

What adoption, reliability, and maintenance teach us after launch.

02

Engineering systems

Reusable patterns for observability, delivery, and dependable software.

03

Studio practice

How product judgment and technical execution meet in real engagements.

Optional analytics help us understand how the site is used. They load only after you accept; rejecting does not affect essential site functions. Learn more