ABD Co.

Admin access

This area is restricted.

ABD Co. Admin dashboard
⚠

⚠ Data fetch issues

    Revenue — last 30 days

      Microworkers campaigns

      Create + track Microworkers basic campaigns, scoped to the active company.

      New Microworkers campaign

      App + keyword

      Targeting

      Volume + pricing

      Budget $0.00

      Advanced (optional)

      Briefing (auto-generated)

      This is the full task description shown to workers on Microworkers (accept/start page).

      Workers upload 2 screenshots as proof per task (account + review/feedback) — make sure the briefing above tells them exactly what to capture.

      New KeyApp campaign

      App

      Target

      Drives organic ranking by funneling installs through a specific keyword search.

      Volume

      ≈ per day —

      Set the total to let KeyApp spread evenly, or fill the daily breakdown below — the total auto-syncs from the sum. You don't need to do both.

      Daily breakdown (optional)

      Reviews

      One per line, format Title|Body. The number of reviews provided should match Total installs.

      Settings

      P&L YTD

      Gross & net revenue, expenses, profit and cash balance per company × month, from January 1 to today. 100% per company (balance total counts your share).

      Bank accounts

      Enter each account in its own currency — total converts to USD.

      • Gross apps — full customer price, before the store's commission. = RevenueCat subscriptions (iOS + Android, gross) + Apple App Store Connect & Google Play direct sales (ex-tax, Now Innov) + ads (AdMob + Huawei + Yandex — ad networks already pay net).
      • Net apps — what actually lands after the store's cut. = subscriptions × store rate (estimated Apple ~0.80 / Google ~0.78 of gross, calibrated from ABD Co.'s real payouts; real Developer Proceeds / earnings where store-direct = Now Innov) + ads (unchanged, already net).
      • Expenses apps — the sum of the Expenses ledger for that company × month. ABD Co. is seeded from the WIO bank statement (real cash): OpenAI, Anthropic, Google Cloud, BytePlus, Microworkers, KeyApp, Murf, Cursor, RevenueCat, Higgsfield, Render, Hostinger, proxies, bank/FX fees…
      • Gross agency (BETECH) — your total take on the BETECH collaboration = Σ (Target Single Profit + Total Dev) from Airtable, converted EUR→USD (× 1.08). The YTD column is the total take to date. Per month: past + current = money already received ("Sent To Partner"), total ÷ elapsed months, in colour; future = still-to-collect (take − received) ÷ remaining months (in colour) + the potential run-rate (take YTD ÷ elapsed months) underneath (grey).
      • Expenses agency — the dev you pay on BETECH = Σ Total Dev (Airtable, × 1.08). Per month: past + current = dev already paid (total − remaining) ÷ elapsed months (in colour, shown −); future = dev still to pay (remaining) ÷ remaining months (in colour) + run-rate (grey).
      • Gross agency (MA) — the MA partner, hand-keyed in USD per month (click a cell to edit). YTD = sum of the months. No expenses.
      • (BETECH & MA exist only under ABD Co.; the Total row shows one merged Gross agency = BETECH + MA.)
      • Profit Apps = Net apps − Expenses apps (apps only). The current month also shows, in grey, the full-month projection (month-to-date profit ÷ days elapsed × 30). Gross / Net / Expenses apps likewise project their future months at this same run-rate (month-to-date ÷ days elapsed × 30), shown in grey.
      • Profit Agency = Gross agency − Expenses agency + MA (agency only). Past + current = net received (received − dev paid) + MA (in colour); future = net still-to-collect spread (in colour) + net run-rate (grey) + MA.
      • Profit Total = Profit Apps + Profit Agency — the grand total. The current month also shows, in grey, the projected total (Projected Profit Total = Profit Apps projected + Profit Agency). Future months show the real still-to-collect + MA in colour, with the projection (apps forecast + BETECH run-rate) underneath in grey.
      • Salary — owner draw ("To Hamza"), 20,000 AED/month for ABD Co. (converted to USD), shown as an outflow (−) below Profit Total and kept separate from Expenses apps. Future months greyed. YTD = total drawn to date.
      • Cash balance — your real bank balance is Cash balance now, edited in the table at the top of the page. The current month = cash now + (apps run-rate + BETECH already received + MA) − salary. Each following month adds (apps run-rate + BETECH still-to-collect spread + potential run-rate + MA − salary), up to the Dec year-end figure — shown as a single total per cell. The Total row counts your share — 100% of ABD Co. / ABD Apps / First Apps, 50% of Qualitechnologies & Now Innov (so for those two the balance rises by only half the Profit Total shown above, which is at 100%).
      • Colours — real money (actuals, received, paid, still-to-collect) is in colour; projections (apps forecast, BETECH run-rates) are light grey. Months marked * are the future; the current month is partial — real month-to-date, with the full-month projection shown in grey.

      Expenses

      Whole-year table — one row per expense × month, from the bank statement. Click a cell to enter/edit an amount. Click a month header for that month's detail.

      New expense

      New tool

      Pending tasks

      Drag onto a day to schedule

      Growth Board

      Read-only · Growth Operator (Phase 0) · last 7 days (rolling) · ranked by $ opportunity

      Loading…

      Track keyword

      App Revenue

      Add RevenueCat app

      Edit store links

      Day Earnings

      App iOS Android Total

      Subscription revenue (RevenueCat)

      App Revenue

      Ad revenue (AdMob)

      App Revenue

      App Store sales (direct)

      App Revenue (gross)

      Month Rank New customers vs M-1 New trials Trials / Customers New paid subs Paid / Trials Paid / Customers Monthly revenue Revenue / customer

      Month Revenue (gross)

      Month Earnings Ad requests Match rate Impressions eCPM Clicks CTR

      Subscription revenue (RevenueCat)

      App Revenue

      Ad revenue (AdMob)

      App Revenue

      Month Rank New customers vs M-1 New trials Trials / Customers New paid subs Paid / Trials Paid / Customers Monthly revenue Revenue / customer

      All months are gross sales from Google's daily sales report (ex-tax, before Google's store commission). The current month is partial — it is the real total month-to-date (through today, with Google's usual 1–2 day reporting lag), not a full-month projection.

      Month Revenue (gross)

      Month Earnings Ad requests Match rate Impressions eCPM Clicks CTR

      Ad revenue (AdMob)

      App Revenue

      Ad revenue (Yandex РСЯ)

      App Revenue

      Month Earnings Ad requests Match rate Impressions eCPM Clicks CTR

      Ad revenue (Huawei Ads)

      App Revenue

      Month Earnings Ad requests Match rate Impressions eCPM Clicks CTR

      App publishing

      A→Z Google Play publishing: Identity → Setup (GitHub / Firebase / GCP / Play / RevenueCat + subs imported to offering default) → MVP (consumes default) → Reskin → Content (listing) → Release (AAB).

      No app published yet.

      Click + New app above to start configuring an app for Google Play.

      —

      copy link
      1

      📋 Essentials

      1.1 Developer account Play Console publication target

      1.2 App identity name + Android package

      🔒 Fill in the Essentials above then Create the app to unlock the Setup and all the following steps.

      2

      ⚙️ Setup

      run each step manually, in order

      Save the app to show the Setup steps.

      📋 Run log OK / FAIL detail + live errors
      
                        
      3

      🛠 MVP

      drop reference screenshots → AI scopes the MVP for every section

      💡 Drop reference screenshots into each section below + paste the Play Store URL, then click Generate — Claude will look at every screenshot and fill all 5 plans for you.

      Reference analysis

      3.1🚀 Onboarding
      3.2💎 Paywall
      3.3🏠 Home page
      3.4📄 Other pages
      3.5⚙ Settings
      🚀 Generate Flutter app code
      Each phase persists its output on the profile. Run them in order, re-run any one, or click ↻ Reset to wipe and restart from B.
      4

      🎭 Reskin

      new icon → reskin texts & colors based on it
      4.1 App icon reference → AI gen → push mipmaps to GitHub
      1 · Reference
      No reference yet
      2 · Prompt + AI generate
      3 · Result + refine + push
      Not generated yet


      4.2 Reskin codebase synonym-rewrite all .arb texts + recolor Material theme from the new icon → PR

      Takes the icon currently in panel 3 above, asks Claude vision to derive a Material 3 palette (primary / secondary / tertiary / surface) from it, and at the same time rewrites every string in every .arb i18n file with close synonyms (preserving keys + ICU placeholders). Pushes both changes as a single GitHub PR on ai/reskin-v{n}.


      4.3 Build & install on phone Cloud Run builds a debug APK · WebUSB pushes it to your phone

      Recommended: Run app (local). The agent (see builders/local-agent/README.md) runs on your machine, clones the repo, builds flutter build apk --debug with your local Flutter SDK, then adb install on the USB-attached phone. No Cloud Run cost, no WebUSB needed. The cloud path below is the fallback (build on Cloud Run + install via WebUSB).

      ↳ Cloud fallback (Cloud Run build + WebUSB install)
      ⬇ Download APK


      4.4 Correct with Claude Code Describe a fix → runs locally on your Max subscription (no API cost)

      Type what you want to fix in the app. The dashboard prepares a Claude Code invocation with full context (repo, app name, palette) and a clone-or-pull preamble. Paste it in PowerShell, Claude Code edits + commits + pushes via your Max subscription, then come back and Build APK in step 4.3 to see the result.


      Copy + paste this into PowerShell:

      
                                
      5

      🎨 Content

      exact mirror of the Play Console flow
      5.1 Privacy policy Dev account URL (reused by all apps)

      Set once on the Developer Account. Edit in Publish → Developer accounts.


      5.2 App access restricted + reviewer instructions (paywall test code)

      Paid features are behind a secret tap. Provide the instructions for the Google reviewers.


      5.3 Ads always "no ads"

      5.4 Content rating IARC rating

      5.5 Target audience 13+ default

      5.6 Data safety collects and shares nothing

      By default: no data collected, no data shared. Override below if needed.

      ↳ Detailed data types (if Yes above)

      5.7 Government apps always no

      5.8 Financial features always no

      5.9 Health always no

      5.10 Category & contact details category + support email (dev account)

      5.11 Set up your store listing icon (Reskin) · feature graphic AI · 5 screens AI · description

      📱 Icon: generated at step 4.1 (Reskin → App icon). The final URL is filled automatically after the GitHub push.


      🖼️ Feature graphic (1024×500)
      1 · Prompt
      2 · Result
      Not generated yet

      📸 Marketing screenshots — upload 5 raw app screens → AI styles them

      The AI takes your raw captures and generates 5 marketing screenshots (phone frame, tagline, styled background).


      Tags (up to 5) 0 / 5


      🚀 Push store listing to Play Console
      Pushes all fields above via the Android Publisher API v3. Run AFTER a first AAB is published on Play Console.
      6

      🚀 Release

      track, rollout, version

      Push a first version (AAB) to Play Console before configuring the products — without a published build, Play does not allow creating subscriptions.

      6.1 Track & rollout Play release channel + % of users

      6.2 Version version code (incremented) + version name (semver)

      6.3 Release notes changelog shown to testers / users

      6.4 Upload AAB upload the signed AAB to Play

      Runs play.upload-aab via the Android Publisher Edits API. Uses the AAB on the chosen branch + the version fields above. This step only uploads — it does not promote.

      6.5 Promote to track promote to track · rollout %

      Runs play.promote via the Android Publisher Edits API. Promotes the uploaded version to the track / rollout % set above. Upload the AAB first (§6.4).

      7

      ⚙ Advanced

      override anything — auto-filled by the pipeline
      7.1 Firebase project + Android app ID + checklist

      7.2 Google Cloud project + SA + APIs + IAM roles

      7.3 Google Play dev account + default track + Play app ID

      7.4 RevenueCat project + API keys + checklist

      7.5 Settings links (in-app) URLs accessible from the app's Settings menu

      7.6 Signing keystore secrets + alias + SHA-256

      7.7 Repository Git URL + branch + CI workflow

      Manage Google Developer accounts. Each account has its own Play Console + Firebase + GCP project. RevenueCat is typically shared across all accounts of a company.

      No developer account yet.

      Click + New account above to register a Google Play developer account with its Firebase/GCP/GitHub/RevenueCat config.

      —

      Architecture: all backend services (Firebase, GCP, GitHub, Play API, RevenueCat) are managed globally via the secrets SA_KEY_ABDCORPORATE, GITHUB_TOKEN, REVENUECAT_LOGIN_EMAIL and REVENUECAT_LOGIN_PASSWORD. All Developer Accounts share them.
      This form captures only what distinguishes this specific Play Console account: its name, its email, and confirmation that the global SA is authorized on it.

      🛒 Play Console — global SA authorization

      The SA automatisation@abd-corporate.iam.gserviceaccount.com must be invited as Admin in this account's Play Console (Users and permissions). Once done, the test button turns ✓ and the orchestrator can publish.


      OAuth user-level token (alternative to the SA). Connect a Google account that has Play Console access to use your individual consent when the SA is insufficient (initial app creation, e.g.).

      💎 RevenueCat — project shared by all apps

      One RC project per dev account. Create it once here (headless Chromium, ~30s) then all generated MVPs inherit the projectId via Setup §2.

      🛡 Data safety — shared declarations (Play Store)

      Global lists (comma-separated) reused by every app on this account. Per-app override possible on the Content form if needed.

      📧 Public contact — shown to users on Play Store listing

      Mandatory to publish on Play. This is the email users can write to for support. Reused automatically by every app published on this account (Content's "Category & contact" phase).

      🔒 Privacy — legal URLs shared across all apps on this account

      Set once, reused by every app published under this developer account. Per-app Data safety (what's collected/shared) is on the app form's Content section.

      ⚙ Advanced — override the global credentials

      Leave empty to use the global credentials. Fill in only if this Developer Account must use Firebase/GCP/GitHub credentials different from the default.

      🤖 Analysis

      No history yet.

        Select a session or click "+ New analysis".

        Summary

        ✅ What's working

          ⚠ Issues

            💡 Recommendations

              📝 My notes & actions

              💬 Questions for Claude

              Analysis in progress…