Agenticly

The Problem

Crypto and markets research still means a dozen tabs — CoinGecko, explorers, news, charts — and no single place to ask a question in plain English and get analytics back. Agenticly was built to sit that assistant on both phone and web, with subscriptions that work on either surface.

What I Built

I was the frontend + payments engineer on a team product — Expo / React Native for phone, React + Vite for web — against Firebase for auth/data and a FastAPI + LangGraph research backend for streaming chat.

• Natural-language queries across crypto (CoinGecko), on-chain (BigQuery), and stocks (Alpha Vantage), with interactive Plotly charts in the chat UI.
• Stock recommendation / analyst-ranking flows alongside freeform research chat (SSE streaming).
• Subscription billing — RevenueCat for App Store / Play purchases, Stripe for web — wired into one Firebase entitlement model so access doesn’t depend on which surface you paid on (including credits, trials, and cancel paths).

Live on Play Store, App Store, and agenticly.app.

Major Features

• NL research assistant — ask in English; get structured analytics and charts, not a SQL console.
• Multi-source data — crypto, on-chain, and equities behind one chat surface on phone and web.
• Cross-platform clients — separate Expo and Vite apps that share the same product flows and billing entitlements.
• Cross-platform billing — RevenueCat + Stripe into a single entitlement truth (pay on web, use on mobile and vice versa).
• Streaming answers — SSE chat so long research replies feel live.
• Product surfaces beyond chat — market trends, scheduled agents (web), settings, and payment history.

Key Challenges

Shipping mobile and web as separate clients (not a forced shared UI kit) kept each surface feeling native while still telling one product story. Keeping subscription UX coherent across RevenueCat and Stripe — different purchase flows, renewals, and failure modes — meant the clients had to read one entitlement truth from Firebase without leaking store-specific mess into the UI.

Results

Agenticly is live on Play Store (10K+ downloads, 4.8★), App Store, and web, with subscription revenue on both mobile and web channels. I owned the frontend surfaces and the Stripe / RevenueCat payment flows as part of the team that shipped the product.

Stack Decisions

Expo + Vite React were chosen for fast dual-platform shipping rather than maximizing code reuse. Firebase kept auth/data overhead low for the clients; the FastAPI/LangGraph backend owns the agent loop. RevenueCat absorbs App Store / Play receipt complexity; Stripe handles web trials and cards — both normalize into one entitlement record the UIs trust.