ComingUp ComingUp
InfluDash

InfluDash

InfluDash: a working, real social-analytics dashboard for creators. Pre-revenue.

Posted on behalf of the maker

Is this your project? Ask us to take it down

Gallery

InfluDash

About

InfluDash is a mobile analytics app for individual social-media creators. It

connects a creator's YouTube, Instagram and TikTok accounts over OAuth and

shows followers, views, engagement and per-post performance over time, in a

Flutter mobile client backed by a FastAPI service. Access is gated behind a

monthly subscription wired to RevenueCat for mobile store purchases.

Under the hood it's a real, layered system, not a prototype: FastAPI with

async SQLAlchemy over Postgres (asyncpg), a clean domain/application/

infrastructure split, four platform adapters (YouTube, Instagram, TikTok, and

a fake adapter used for local development and demos), JWT auth with

envelope-encrypted credential storage, and a Flutter client that runs on

Android (a signed release build exists) and in the browser. The backend

carries 566 passing unit tests.

It is built and verifiably runnable, not just claimed to be: two independent

agents, each starting from a genuinely fresh git clone with no prior project

knowledge, brought up the full stack with docker compose up and

scripts/seed_demo.py, and — with no help and no prior context — got the

backend serving real seeded data over HTTP and the Flutter client compiling

and actively served, on the first attempt. That's proof at the data and

build layer, not a visual one: nobody has yet watched a populated dashboard

screen render on a device or in a browser.

What it is not: it has zero users, pre revenue, and has never been

published to any app store or web store. This is a pre-revenue codebase and

operational asset — the product of real engineering work, not a business

with customers or cash flow. Buy it for what's built, not for existing

traction.

Why it's for sale: the operator works full-time at a company. A paid

app on Google Play requires the developer's legal name, email, street

address and phone number to appear publicly on the store listing, which the

operator is not willing to expose while employed elsewhere — a constraint

tied to the operator personally, not to the product or the code. A buyer

already operating a business doesn't have that problem.

Comments (3)

Candida Greenfelder Candida Greenfelder 1 month ago

is it just me or does tracking all those accounts sound like a full-time job?

Darrel Franecki Darrel Franecki 1 month ago

pre-revenue is a red flag, what's the plan for monetization and how do you stack up against competitors?

Hayden Terry Hayden Terry 1 month ago

finally, a dashboard that gets all my socials in one spot. can’t wait to see the stats!