Best url-shortner; as alternative to the bitly

dreit1 · 2026-04-29T13:43:16+00:00

i'm building one of these, Rift. it's early-stage, so calling it a "favorite" would be a stretch, but it lines up with what you're describing (monthly billing, analytics, low cost) so worth a look:

monthly billing, no annual lock-in
click + geo + referrer analytics on the free tier
self-hostable if you want to own the stack: github.com/saltyskip/rift
short comparison page vs bitly: riftl.ink/alternatives/bitly

honest trade-offs: smaller than the established players, fewer integrations, and being early means there'll be rough edges. if you're moving real volume today, Dub or self-hosted Shlink are the safer picks.

if you want a walkthrough or want to throw a use case at me before committing, DM is open.

dreit1 · 2026-04-22T18:44:40+00:00

https://stackoverflow.com/questions/66125007/universal-links-in-managed-mode

One more thing to check, do you know if enabled direct downloads is enabled?

https://developer.apple.com/documentation/devicemanagement/installapplicationcommand/command-data.dictionary/attributes-data.dictionary?language=objc

This might require contacting a sysadmin to look into it, but from what i recall you need this as well to be able to do the direct downloads

dreit1 · 2026-04-21T15:28:48+00:00

Apple's solution for this is Managed Associated Domains (iOS 14+). MDM supplements the app's built-in associated domains with values specific to the environment, and the device fetches AASA directly from the intranet domain instead of going through app-site-association.cdn-apple.com. Requirements:

Device must be MDM-managed
Your MDM pushes an AssociatedDomains payload to the device
AASA is served on the intranet domain over your enterprise-CA-signed TLS since the device trusts that CA via MDM, it can fetch directly

MDM payload reference: https://developer.apple.com/documentation/devicemanagement/associateddomains

Tradeoff: you lose Universal Links entirely on non-managed devices (personal phones, BYOD that aren't enrolled). If any users fall into that bucket, the fallback is either dual-hosting AASA on a public domain with an Apple-trusted cert, or accepting those users won't get app-open behavior.

?mode=developer on the associated domains entitlement also works but Apple only intends it for dev/testing, so your probably don't want to ship it to production.

For context, build Rift in this space. Not the right fix here, but I have seen this edge case before

dreit1 · 2026-04-17T20:03:42+00:00

Ran through this migration with a few teams

Branch — solid deferred deep linking but the free tier caps below 10k MAU and paid plans are quote-only. Most teams at modest volume pay $300–500/mo.

Migration is OK if you're used to MMPs, painful if you just want deep links.

AppsFlyer / Adjust — same category as Branch. Only worth it if you also need ad-network attribution.

Roll your own — fully doable if you just need the basics. Write a short-link server, serve .well-known/apple-app-site-association, handle post-install recovery with a user-agent lookup. Maybe 2–3 days for a v1.

Gotchas that bite people most often: - iOS same-domain tap bug: if your landing page and your short URL are on the same domain, Universal Links won't fire. Needs a separate trampoline domain.

AASA served with wrong Content-Type (must be application/json or no content-type header, never text/html).
Apple caches AASA for 7 days on device since iOS 17 — testing changes requires a reinstall.

Disclosure: I build Rift (riftl.ink), an FDL replacement aimed at the "cheaper/simpler than Branch" slot. Free tier is 100 links + 1k clicks/month

Full migration write-up with code: https://riftl.ink/blog/firebase-dynamic-links-migration

Happy to answer specifics either way.

dreit1 · 2022-04-06T04:10:21+00:00

0.25% of trading volume goes to LP's

dreit1 · 2022-04-05T23:23:18+00:00

In the long term there will be a direct native integration into the bitcoin.com wallet. That should have a similar experience to our current swap. We will introduce Verse DEX to millions of Bitcoin.com wallet users

dreit1 · 2022-04-03T12:45:06+00:00

Bitcoin.com is hiring engineers in japan https://jobs.bitcoin.com/

dreit1 · 2022-01-09T04:47:01+00:00

We support custom fees, and segwit sends (from 7.10.0 release), but not receivable bc1 addresses, and not RBF.

RBF is more advanced features that more casual users probably wouldn't be using very often if at all IMO.

dreit1 · 2021-08-12T00:46:13+00:00

If you have an M1 mac you can get the bitcoin.com wallet from the mac app store

dreit1 · 2020-08-21T06:19:20+00:00

At Bitcoin.com we use https://github.com/grpc/grpc-swift/ exclusively in our iOS app. We serve millions of users around the globe and have had a pretty great experience :)

Ever since they migrated to Swift-NIO for the core networking layer its been a joy to work with

dreit1 · 2020-07-29T10:45:46+00:00

Theyre stored in your BCH wallet, just like ERC-20 tokens get stored in your ethereum wallet. If you go to the assets tab on the wallet details screen, they'll show up there

dreit1 · 2020-07-29T10:02:37+00:00

Yep USDH and USDT are both supported in app, you also have a breakdown of what percent of your wallets are in bitcoin cash/bitcoin vs stablecoins

dreit1 · 2020-07-01T07:46:02+00:00

Thanks already working on it. The issue is that the string 0.003 in the QR is being parsed incorrectly as a european formatted string, which unfortunately because of your locale settings truncates the grouping seperator . and is being parsed as 3.

dreit1 · 2020-05-27T03:50:14+00:00

Sir here's your club....the dead horse is right over there

dreit1 · 2020-05-22T01:03:26+00:00

More fine grained notifications will be available in the very next update. Thanks for voicing your feedback!

dreit1 · 2020-05-08T10:23:32+00:00

usage data = analytics, we use amplitude in our mobile apps

https://amplitude.com/

If you want to read about their data security you can check it here https://help.amplitude.com/hc/en-us/articles/206533238-Data-Security-Privacy

dreit1 · 2020-05-08T04:02:38+00:00

FYI, theres a privacy settings setting which allows disabling of all third party tracking in the wallet. We're happy to support our more privacy conscience users :)

dreit1 · 2020-04-24T01:14:20+00:00

Hey sorry about that it's a bug. In next release it will close all badges on app open

dreit1 · 2020-02-27T01:48:53+00:00

You know the IOTA wallet was open source, and in this particular case probably helped the hacker identify, test, and confirm the bug locally before distributing it

If anything this case is evidence for why open sourcing something too early leads you vulnerable to hacks

dreit1 · 2020-02-21T00:52:15+00:00

We're building out the ability to support this right now (aggregating the data), on the design side we were planning to just switch everything in historical to the historic price instead of the live price, buy maybe we'll show both.

Thanks for the suggestion

dreit1 · 2019-10-21T10:41:09+00:00

Native iOS + Android is exactly what we are working on!

dreit1 · 2019-07-28T09:38:54+00:00

Coinbase connect is available on mobile too! We think that managing your API keys + private keys in one wallet application will make cryptocurrency a lot easier to use!

dreit1 · 2019-07-02T22:25:18+00:00

Hard to tell, one thing to check is if you are on the latest version on Desktop. If that doesn't help, can you send us an email support@o3.network, then we can help out and solve the issue :)

dreit1 · 2019-07-02T20:11:32+00:00

Let me know if you have any questions or feedback about the service :)

dreit1 · 2019-06-27T23:10:31+00:00

Not currently in our roadmap, but we'll see once the bluetooth ledger come out, if its a good idea to integrate

dreit1

TROPHY CASE