Product review · 8 October 2026

Point Zero, through a product owner’s eyes

I went through the iOS app the way a new user would: open it, sign up, look around, set up a profile and go through settings. This page covers what I found, how I would fix it, a two-week plan with the team, a concept of the result, and what comes after.

Prepared by Mustafa Dabaibeh for the Technical Product Owner role

Findings
36
High severity
10
Addressed in two weeks
29
Screens captured
35

At a glance

Five themes, one opportunity

Most findings trace back to five themes. Four are problems to fix. The fifth is the strongest thing Point Zero already has.

How I reviewed

One afternoon, as a new user

Device

iPhone, live App Store build, 8 October 2026, screens captured through iPhone Mirroring.

Path

First launch, login, sign-up and password reset, Home, Rollz, Search, notifications, messages, profile, edit profile and settings.

Left out

Posting, live, the wallet, Android, and anything that touches other users. I didn’t post, follow, like or message anyone.

Severity

High blocks growth, trust or compliance. Medium is friction most users notice. Low is polish.

HighMediumLow

Effort

A rough guess for one engineer before seeing the code. S is under a day, M two to four days, L more than a week.

Findings

What I saw and how I’d fix it

Each finding has the evidence, why it matters, and a fix that covers both the product and the engineering side. Select a screenshot to enlarge it.

Severity
Timing

Showing 37 of 37

Two-week plan

Ten working days with the team

Week one is about understanding the product and laying foundations. Week two rebuilds the first five minutes on top of them. Day 10 ends with a release candidate the team can test, not a slide.

Week 1Understand and lay foundations

  1. Day 1
    Meet the team, get access

    Repos, analytics, crash reports, App Store Connect and Play Console. Agree what success looks like for the two weeks.

  2. Day 2
    Set the baseline

    Map the funnel from first open to first post, plus crash-free rate and cold-start time. Fill the gaps in event tracking.

  3. Day 3
    One ranked backlog

    Merge this review with what the team already knows, rank by impact and effort, and agree a definition of done.

  4. Day 4
    Design system v0

    Colour, type and spacing tokens, one navigation bar, a bottom bar inside the safe area, one icon set and an empty-state component.

    N1 N2 N3 N6 N8

  5. Day 5
    Quick fixes ship

    Launch screen, app icon, password autofill, forgot-password email, the Terms link and one copy deck.

    F1 F2 F7 F9 F11 T1

Week 2Rebuild the first five minutes

  1. Day 6
    New sign-up

    A stepped flow, one verified identifier, signed in on success, and the platform Apple and Google buttons.

    F4 F5 F6 F8 F10

  2. Day 7
    Introduction and AlgoZero

    Three intro screens, an interest picker, a Tune your feed entry on Home and “Why am I seeing this?” on posts.

    F3 A1

  3. Day 8
    Profile

    One Edit profile screen, a Finish your profile card, a readable header on any cover, and one Create entry point.

    P1 P2 P3 P4 N4 N5

  4. Day 9
    Settings and trust

    Settings grouped by task, Log out and Delete kept apart, verification labels, languages in their own script, a name filter and Report account.

    P6 P7 P8 P9 T2

  5. Day 10
    Release candidate

    QA in English and Arabic on small and large phones, a TestFlight and Play internal build, a demo to the team, a retro, and an agreed 90-day plan.

What the team has on day 10

  • A release candidate in TestFlight and Play internal testing
  • Design system v0, documented
  • One ranked backlog
  • A funnel dashboard with a baseline
  • A 90-day roadmap everyone agreed to

Assumptions

  • A small team: two mobile engineers, one backend engineer and a designer
  • Releases can go to TestFlight during the trial
  • If the team is different, day 1 resizes the plan

Dependencies

  • An SMS provider for phone verification (F4)
  • Terms of Use and Community Guidelines text from legal (T1)
  • Access to analytics and store consoles on day 1

The result

How Point Zero could look after two weeks with the team

A clickable concept of the release candidate. Switch between today and after for each screen. The after screens respond: go through the intro, sign up, tick off the profile card, or tune the feed with AlgoZero.

After · concept

After

A concept prototype built for this review. Sample accounts and content are illustrative. The PointZero logo comes from pointzeroapp.com and is used only to show the concept in the app’s own brand. It is not the live app and not an official Point Zero design.

After the trial

What I’d work on next

The two weeks fix the entry point. The next ninety days finish the foundation, grow the core loop, and prepare the platform to scale.

Days 15 to 30Finish the foundation

  • Move every screen onto the design system
  • A full Arabic and right-to-left review
  • Rollz as a full-screen pager (N7)
  • Help centre and Report a problem (P10)
  • A moderation queue with response targets
  • Performance budgets for cold start, crashes and API latency

Days 31 to 60Grow the core loop

  • AlgoZero across the app, not just behind the logo
  • A creator programme that rewards original posts
  • Feed ranking for freshness and variety (T3)
  • A notification plan with frequency caps
  • Invite friends from verified contacts, with consent

Days 61 to 90Prepare to scale

  • A video pipeline: transcoding, adaptive streaming, CDN
  • Feed precomputation and caching
  • Search and hashtags that index well in Arabic
  • Feature flags and A/B testing
  • A weekly release train with staged rollouts

Product ideas

Ideas I would bring to the roadmap discussion. Each one builds on what makes Point Zero different: users decide what their feed shows.

AlgoZero weekly recap

Once a week, AlgoZero shows what changed in your feed and asks whether to keep it. It builds the habit and gives the team explicit preference data.

Why this post, everywhere

Every post can explain itself and be tuned from the same menu: more like this, less like this, never this account.

Feed modes

Following only, Latest first, or Tuned. A visible switch on Home that matches the promise of user control.

Local discovery for Jordan

Places, food, events and sport in Amman, Irbid and Aqaba, Arabic first, with creators as the guides.

Creator studio

Simple analytics, an Original badge, and a path into the Growth programme for creators who post here first.

Safety you can see

Clear reporting with status updates, reviewed verification, and a public summary of moderation actions. Trust becomes a feature.

Scaling properly

What has to be in place before growth

Growth exposes every weak joint at once. This is what I would put in place, or confirm is already there, before pushing acquisition.

Product practice

  • One roadmap tied to metrics. Every item names the number it should move.
  • A short spec per feature. Problem, users, success measure, out of scope, in English and Arabic copy.
  • Design and copy review before build, in both languages.
  • Release notes for every version, internal and in the store.

Platform

  • Media pipeline. Upload, transcode to adaptive streams, serve from a CDN, detect duplicates.
  • Feed service. Candidates plus ranking, with AlgoZero preferences as explicit signals and cached timelines.
  • Versioned APIs and a minimum-version policy, so old app builds keep working or update cleanly.
  • Feature flags for every risky change.

Reliability and data

  • Service targets for API latency, error rate and crash-free sessions, with alerts and an on-call rota.
  • One event dictionary shared by app and backend, so funnels mean the same thing everywhere.
  • Dashboards for activation, retention, creator health and moderation.

Trust, safety and privacy

  • Published rules. Terms of Use, Community Guidelines and a takedown process.
  • Report, block and appeal flows with a moderation queue and response targets.
  • Hash matching for known illegal media, and reviewed verification badges.
  • Data protection in line with Jordan’s Personal Data Protection Law (2023) and the UAE’s PDPL, including retention and deletion.

Team and delivery

  • Two-week cycles with planning, a demo and a retro.
  • A definition of done: design, both languages, analytics events, tests and release notes.
  • Automated tests on the core flows, run on every change.
  • Staged rollouts on both stores, watched against the service targets.

What I’d measure

The numbers I would own

Targets get set on day 2, once there is a baseline. Setting them before seeing the data would be guessing.

MetricDefinitionWhy it matters
Sign-up conversionShare of first opens that finish sign-upMeasures the first five minutes directly
ActivationNew users who follow three or more accounts and view ten or more posts on day oneThe best early sign that someone will return
RetentionDay 1, day 7 and day 30 return rates by sign-up weekTells whether the product keeps its promise
Tune rateShare of weekly active users who adjust AlgoZeroShows the differentiator is being used
Creator healthWeekly posting creators, and the share of original postsA feed is only as good as its supply
QualityCrash-free sessions, cold-start time, API p95 latencyUsers judge quality before features
TrustMedian report response time, impersonation takedownsSafety problems compound with scale

Questions

What I’d ask on day one

Parts of this review are inferred from the outside. These questions turn them into facts.

  1. Where does the funnel lose people today? First open to sign-up, to verified, to first follow, to first post.
  2. What is the stack, and how do releases ship? Client framework, backend, CI, and how often builds reach the stores.
  3. What moderation exists, and who handles reports? Tools, queue, response times, and how impersonation is caught.
  4. Who is on the team, and how is work planned now? So the two-week plan fits the people, not the other way round.