A living view of what's shipping, where each project stands, and the timeline ahead. Click any project to expand.
The Android launch is the program's primary focus right now. From next week we begin spinning up the other verticals in parallel — platform audit, automatic license verification, nano-banana, the design system, and the future platform roadmap.
Android first. Google account verified; preparing to list the latest stable build and burn down the critical bugs. 41 tickets advanced to In Review this week (12 merged in today’s run) + a fresh QA build shipped.
QA the 26 Jun build · clear the external config blockers · then, from next week, stand up the other verticals alongside Android.
Public Play listing is gated by external approvals (Play Data Safety, legal/deletion pages). YouTube API access + Google's 90-day clock are the other external gates.
Projects
Jira · where we stand · 26 Jun
122 bugs · 25 features · 32 tasks · 9 epics · priority: 13 highest · 24 high · 146 medium · 5 low
Where it's headed. Google account verification is cleared. The plan now is to list the latest stable build (it's ready) and burn down the remaining critical bugs, while the automated runs keep clearing the backlog.
iOS ↔ Android parity. I identified a set of parity gaps in Mohammed's Android code where it had fallen behind the iOS repo. A large share are already handled (done / in QA) and several are tied to this release — the live count and the remainder are tracked in Jira under the parity epic (ANDROID-98) and the parity-labelled tickets.
This week — 41 tickets advanced to In Review. Across multiple automated + manual passes (logout/ghost-session, keyboard & OTP, YouTube connect, review uploads, account-status routing, iOS-parity gaps, and more), 41 ANDROID tickets were moved to In Review. The latest fix→test→merge pipeline worked the backlog in priority order (skipping the 34 already auto-fixed, awaiting-QA tickets); of 25 tickets picked in that run, 12 were fixed, device-verified on real hardware, and merged to main: crash reporting (Sentry) + a root error boundary, iOS-parity modal styling, the notification-permission prompt moved off the OTP screen, working Terms/Privacy links, license-PDF thumbnail, offers refresh on foreground, offers-list scroll restore, bold sold-out styling, the rejected-image info icon, the exempted-review orange tick, profile back-navigation, and offer-detail rendering.
Routed for follow-up. 6 more fixes sit on branches in Develop awaiting manual QA; 1 failed its device test and is flagged for rework; 10 duplicate tickets were linked. 7 tickets are blocked on external setup (configuration, not code) and were moved to To Do with notes (listed at right).
→ Jira board (ANDROID) → recently updated → CEO launch deck → dev deep-dive → Jira revalidation
Milestones
Blocked · needs owners (in To Do)
What it is. A privileged Google API (Creator Partnerships / brandconnect) that gives alist consented, non-public YouTube creator + video insights and an official brand-deal reporting channel that surfaces in the YouTube Studio app, far beyond today's public Data API v3 integration.
Status — partly done. The initial scope is complete. The project is now blocked pending access to the API — we can't run the actual data tests until that access is granted.
CEO requirement, by design. Google's own developer policy requires this data be ephemeral: refresh within 7 days, store 30 days max, with a deletion path. That maps cleanly onto the directive that Google data must not live in the existing database — the architecture is a separate, siloed, auto-purging insights store.
For a walkthrough of the integration scope, ask Vineet for a call.
Milestones
Blocked
Pending access to the Creator Partnerships API to run actual tests. Confirm the 90-day contract start date so this clock can be dated.
Scoping is done and it's now in active development. Automatically verifies an influencer's trade/business license rather than relying on manual review. Vineet is building it.
The new design is already done. Luisa requested some additional changes; these need to be wired in within support and are awaiting Vineet to fix the APIs. The guidance has been not to modify the core platform, so the changes are being handled around it rather than in the platform itself.
A cloud-based design system for A-List.
Disclaimer
Jacob is strongly resistant and has expressed a strong disinterest in continuing — he was very firm about it. Progress is effectively blocked on that, and it's flagged here as the current status.
A full audit of the A-List platform — security, target architecture, cross-repo correlation, and SEO/GEO — consolidated into one detailed consultant write-up.
Next step. Break the audit into subtasks and allocate VPN to execute them; support is also involved. The most detailed write-up is linked below.
Scoping the next-generation A-List platform direction. Awaiting additional database access from Subin and VPN before it can go deeper — but exploration is already underway.
⚠ Heavy work-in-progress — directional only, not final
Bars are indicative. Android is the active focus; the other verticals spin up from next week. Google spans the signed 90-day window (start date to confirm).
alist program status · internal · update via the _status-dashboard project (see CLAUDE.md)