pull down to refresh
0 sats \ 0 replies \ @posilicious 6 Apr \ on: Will the App Store reject our app if it incorporates zaps? bitcoin
Within the last few months, I've seen:
- In iOS store, an app with nostr "twitter" functionality that allowed crypto transfer, not a zap but a wallet transfer nonetheless, and another app that allowed just allowed a wallet transfer. The latter had a busy UI and made no mention of crypto transfer. The former just provided a wallet address that allowed the user to fund the wallet. Both had minimal users. A while back I saw an iOS app that was submitted and had the bluetooth libraries that the user couldn't access even via A/B or any means and made no mention of bluetooth in the store description of website. The bluetooth was detected, presumably via static analysis, and app was rejected for noncompliance... Since nostr clients are fundamentally mostly websockets and json, it wouldn't surprise me if the functionality wasn't detected by static analysis.
- Approved for Android store: apps that also included nostr NIP-01 functionality, allowed crypto transfer (again not NIP-57) and one of them even had in-app purchase set in the play store submission. Again both had small userbase.
As suggested in other posts, I think you'll have a harder time once you reach a Primal or Samourai wallet user base.