Fresta
Senda
OmniWell
Apps
Fresta, Senda and OmniWell are the current StorySpark products I maintain end to end, from release flow to public support.
Sup! I'm Paulo Henrique
StorySpark
Founder
StorySpark
Mobile
Web
Brazil
I build mobile and web products through StorySpark.
Right now I'm shipping Fresta, Senda and OmniWell, while
keeping the public surface stable for every release.
Read the latest post
Shipping Three Products Without Breaking the Public SurfaceProjects
I keep the homepage lean and let each block open into its own page, the same way the reference handles apps and web work as separate surfaces.
Fresta
Senda
OmniWell
FUT LIGA SC
NeuroPad
Experience
This is the operating side of my work: product direction, launch support, frontend craft and the boring-but-critical public routes that keep apps review-ready.
StorySpark
Founder · product, frontend and release systemsBuilding the umbrella that holds the apps, the portfolio, the legal routes and the support surface in one coherent system.
OmniWell
Health productA fuller wellbeing product with onboarding, profile structure, communication flows and a visual system built to feel complete.
Senda
Content + communityA spiritual product line built around daily publishing, premium access, content rhythm and a calmer community-facing experience.
Fresta
Calendar platformFestive calendars, campaign organization and operational clarity for a product that has to feel useful, light and easy to keep fresh.
Public support surface
Review-ready routes and contact pathsPrivacy pages, data deletion guidance and stable contact routes maintained as part of the product, not as an afterthought.
Skills
The stack is intentionally compact. I care more about a tight set of tools that can ship and keep running than an inflated wall of buzzwords.
Mobile
iOS-first product work with careful flow and polish.
shipping now
SwiftUI
Interfaces, navigation and daily product iterations.
core practice
Mobile UX
Readable flows, calmer hierarchy and store-ready screens.
Web
Frontend and backend choices for product surfaces that stay stable.
frontend
Next.js
Structured pages, route organization and fast iteration.
frontend
React
Composable UI for product and support-facing surfaces.
typed UI
TypeScript
Safer iteration for apps, tooling and reusable logic.
backend
Supabase
Auth, data and product plumbing without unnecessary weight.
Product
Enough design and writing to keep the product voice coherent.
interface design
Figma
Layout studies, flows and visual refinement before build.
decision making
Product strategy
Scope control, feature priorities and public positioning.
public layer
Writing
Launch notes, blog posts and legal copy with a clear voice.
Infra
The small systems that make the visible product reliable.
deploy
Docker
Predictable containers for the portfolio and support routes.
routing
Traefik
Subdomain routing and TLS without turning ops into drama.
workflow
GitHub
Source control and deployment handoff for small, fast cycles.
support layer
Legal docs
Privacy and deletion routes shaped as product infrastructure.
Blog
The reference also had a writing layer, so this portfolio now does too: a small set of posts around shipping, public surfaces and product decisions.
Latest post
Shipping Three Products Without Breaking the Public Surface
What changes when you stop treating release notes, legal pages and support routes as admin work and start treating them as product.
Read postNew note
Why Privacy Pages Are Part of Product Design
A short note on why these pages influence trust, review stability and the feel of the whole product.
Read postBuild log
Building Mobile and Web Under the Same Roof
Why I prefer a smaller system where apps, portfolio and support surface evolve together instead of drifting apart.
Read post