Need honest feedback on my Dub app review experience

Apps
1

I recently tried the Dub app and wrote a detailed review, but I’m not sure if I’m being too harsh or missing key features that others find useful. I’m looking for help understanding if my experience is typical, what I might have overlooked, and whether the app is worth sticking with or uninstalling. Any insights, tips, or comparisons to similar apps would really help me decide what to do next.

2

Your experience with Dub sounds pretty typical from what I have seen in other threads and reviews.

Here is a simple way to sanity check your review and spot gaps.

  1. Check if you covered the core value

    • Dub is mainly about short links, analytics, branded domains, and API.
    • Ask yourself if you judged it as a link tool or as something broader.
    • If you compared it to Linktree or full marketing suites, your expectations might be off.

  2. Common things users miss

    • Rate limiting on free plans. People think links are “broken” when they hit limits.
    • Click analytics delay. Some stats do not feel real time.
    • Team features and workspaces. Many do not open those menus at all.
    • Integrations via API or Zapier. If you do not use those, you miss a lot of what heavy users like.

  3. What other users tend to like

    • Simple interface. Less clutter than some older link tools.
    • Branded domains support.
    • Decent link analytics for campaigns.
    • Privacy focus and open source angle. Tech people care about this more than casual users.

  4. Where people complain

    • Onboarding does not explain limits well.
    • Some UX flows feel confusing, like domain setup or advanced options stuck behind small icons.
    • Mobile experience feels weaker than desktop for serious setup work.
    • Support answers feel slow on lower pricing tiers.

  5. How to check if you were “too harsh”

    • Look at your review and count how many points are about:
      a) Bugs or slow parts.
      b) Missing features you expected.
      c) Poor explanation or unclear UI.
    • If most of your criticism is “I did not know it had this” or “I could not find this” it is more a UX and onboarding problem.
    • If you hit real errors or broken behavior, then your harsh tone is fair.

  6. A balanced way to phrase your review

    • Start with what worked: “Link creation was fast. Basic tracking worked.”
    • Then your pain: “Domain setup felt confusing. I had to guess settings.”
    • Add context: your use case, like solo creator, agency, growth person, etc.
    • Close with “This might fit users who need X. It felt weak for Y use case.”

  7. What you might have missed

    • Advanced link features like A/B, geo targeting, device targeting, or tags.
    • Export of data or integration with your analytics stack.
    • Workspace or team management if you only tested as a single user.

If you want more direct feedback, paste your review in the thread and say:

  • Your use case.
  • What tools you used before.
  • What plan you tested.

Other users can then say “yeah, my experience matched yours” or “I use it in a different way” and you will see if your take leans niche or common.

3

You’re not crazy for wondering if you’re being too harsh. With tools like Dub, expectations drift all over the place.

Where I slightly disagree with @sterrenkijker is on the “typical” part. A lot of Dub experiences depend heavily on why you’re using it:

  • If you came from Linktree / Card / full funnel tools, Dub can feel oddly barebones or “cold”, even if it’s doing its main job fine. That doesn’t make your review unfair, it just means you judged it as part of a stack, not as a standalone link shortener.
  • If you’re more technical or used to APIs and dashboards, you might actually feel the opposite: “solid core, weird UX, I’ll live with it.”

A few concrete ways to sanity check your review that don’t repeat the step list already shared:

  1. Re-read your review and highlight:

    • Things that actually blocked you (could not complete task).
    • Things that were just annoying (extra clicks, unclear labels).
    • Things that were preference (you like different styling, layout, etc).

    If most of your harshness is in the “blocked” column, then no, you’re not too harsh at all.

  2. Check if you judged it against the pricing you used.
    Free plan + expecting polished onboarding, instant support, and advanced targeting is going to lead to a harsher tone than most paid users will have. That’s not wrong, but it’s context you should probably make explicit in the review.

  3. Look at your time horizon.
    Did you use it for 30 minutes or 3 weeks?
    Short tests often produce reviews like “confusing, missing X” that would soften after actually running a small campaign and seeing that the analytics and links do their job fine once set up. If you only had a brief session, I’d flag that clearly so others read your review as “first impressions,” not a long-term verdict.

  4. Compare your use case with what Dub seems to be optimizing for:

    • If your use case is “creator with one main bio link”: you might have wanted landing pages, themes, link scheduling, etc.
    • If your use case is “marketer managing 100+ campaign links”: you probably care more about tags, UTM, exports, per-link analytics, API.
      If your pain points are all in category A but Dub’s strengths are in B, that explains the mismatch without invalidating how it felt to you.

  5. Pay attention to what surprised you.
    Surprises are often where your review is most valuable:

    • “I expected X from the marketing page but got Y.”
    • “I didn’t realize there were rate limits until my link ‘broke’.”
      Writing those as “Expectation vs Reality” instead of “This app sucks” keeps it honest but less brutal.

  6. One specific thing you might have missed that a lot of non-power-users skip:

    • Tagging / organizing links
    • Any form of targeting (geo, device, rules)
    • Workspace logic if you’re used to just 1 account = 1 environment
      If your review complains that things feel “too simple” or “too limited,” it might be worth quickly checking whether you never touched those options. You can even mention in your review: “I didn’t use A/B or targeting, so can’t speak to those.”

If you want people to really pressure-test your tone, post:

  • A copy of your review
  • Your use case in one line: “small biz owner running ads,” “YT creator,” “growth person at startup,” etc.
  • How long you actually used it and which plan

Then folks can tell you straight up: “Yep, this matches my experience” or “My workflow is totally different, here’s why I still like it.” That’s usually the fastest way to see if you’re an outlier or just saying what a lot of people think but don’t phrase as sharply.

So no, being harsh isn’t inherently unfair. The key is: are you harsh and specific, with your expectations and context spelled out? If yes, that’s exactly the kind of review most of us want to read, even if Dub’s fans won’t love it.

4

Quick analytical take on your Dub review:

  1. Your experience “typical” or not?
    Dub sits in a weird middle ground: not as “page builder” as Linktree, not as hardcore as enterprise link trackers. So wildly different reactions are actually normal. @sterrenkijker is right that context matters a lot, but I’d push further: Dub’s positioning and marketing often imply more polish and breadth than the current UX delivers. So if you judged it by what the homepage promised, your harsher tone might actually be closer to what many silent users feel.

  2. Where you might be underrating Dub
    These are features a lot of reviewers miss on first pass, especially if they’re focused on aesthetics or onboarding:

    • Per link analytics beyond just “clicks”
    • Tagging and search when you have dozens of links
    • Workspace separation for client / project work
    • API usage for people who automate campaigns

    If your review barely touches analytics, organizing links, or workspaces, you might be underestimating Dub’s long term value for “power user” scenarios.

  3. Where you might be overrating your negative experience
    Places I see reviews go too hard:

    • Judging it like a landing page builder instead of a link shortener + tracking tool
    • Calling the product “useless” just because it lacks themes or deep customization
    • Treating “I got briefly lost in the interface” as a fatal flaw instead of a 1-time learning curve

    That does not mean you should soften your criticism, but you can make it sharper by saying: “For creators wanting a visual bio page, Dub feels too minimal” instead of “Dub fails as a product.”

  4. How to tighten your review without redoing it
    You already wrote a detailed review, so think in terms of quick edits, not a rewrite:

    • Add a 1‑line “who I am” and “what I used it for” at the top.
    • Add a small “What Dub did well for me” section even if it is short. It gives readers calibration, not positivity.
    • Add a one‑sentence note on usage time and plan: “Free plan, used for X days for Y purpose.”
      These tiny pieces of context prevent readers from seeing your review as a rant and instead as targeted feedback.

  5. Your review vs other users’ expectations
    A useful framing you can literally copy into your review:

    • “If you are a creator who wants a single polished bio link page, my complaints about Dub will probably resonate.”
    • “If you are a marketer or dev who cares about tracking and managing many links, you may care more about features I did not fully test, like tags, workspaces, and deeper analytics.”

    That keeps your harsh points intact and also explains why someone like @sterrenkijker might have had a smoother time.

  6. Pros & cons to make your review more balanced

    For clarity, something like this works well around Dub in general:

    Pros of Dub

    • Strong core link shortening & tracking once configured
    • Useful tagging and organization when managing many links
    • Workspaces make sense for agencies or multi‑project setups
    • API & more “technical” features that fit growth / marketing workflows

    Cons of Dub

    • UX can feel dry or confusing for non‑technical or “bio link” users
    • Onboarding and discoverability of advanced options is weak
    • Marketing can imply a broader, more polished experience than what new users see
    • Free‑plan users may feel friction around support, rate limits or “missing” power features

If your existing writeup already hits those cons and only lightly acknowledges the pros, you are not being “too harsh,” you are just being incomplete on the upside. Add a clear pros/cons block, spell out your use case, and keep the criticism sharp. That kind of Dub app review ends up far more useful than a neutral, vague 3‑star take.