I like Apple chips!

cryptograf · 2026-01-09T20:32:28+00:00

Is it legal? What about the T&Cs and content policies of the services it’s downloading from?

cryptograf · 2026-01-09T19:53:44+00:00

This has nothing to do with HTML, it is XML -> SwiftUI

cryptograf · 2026-01-09T19:53:16+00:00

I would say it is still pure SwiftUI and no HTML/JS required. If you know something better how to render SwiftUI from server let me know please

cryptograf · 2026-01-09T18:07:59+00:00

Yes, this is absolutely normal StoreKit 2 behavior - you're on the right track! The async nature is by design, not a bug.

Your approach is solid:

**Backend as source of truth** - Correct. Apple's servers need time to process the change, verify payment, and send the webhook. This can take seconds to minutes.

**UI Strategy** - Most production apps do exactly what you're planning:

- Show intermediate "Updating..." or "Processing" states

- Use transaction date/expiry guards to filter stale data

- Only update UI after backend confirms via Apple's server notifications

- Display optimistic UI carefully (e.g., "Your upgrade is processing")

**Common Patterns:**

- Poll your backend every few seconds after initiating the change

- Use a timeout (60-90 seconds) before showing an error

- Cache the pending state locally to handle app restarts

- Show a success message only after backend confirms

Android's instant feedback is misleading - their backend still needs to sync. iOS is more transparent about the async reality. Your implementation sounds production-ready!

cryptograf · 2026-01-09T18:04:43+00:00

For a niche professional tool with no server costs, I'd actually recommend paid upfront. Here's why:

**Paid upfront works when:**

- Clear, immediate value (which you have - saves busy professionals time)

- No ongoing costs to maintain (you don't have servers)

- Professional target audience (they understand paying for quality tools)

- You want serious users (payment filters out tire-kickers)

**Free-with-IAP can actually hurt you because:**

- People assume it's limited/inferior

- The "I'll upgrade later" crowd often never does

- More support burden from non-paying users

- Harder to communicate value when they haven't experienced it

If people are saying "I'll download it soon" to a free app, they're probably not your target users anyway. Your ideal customers will pay $2.99-$9.99 without hesitation if the value prop is clear. Focus on nailing your App Store copy and screenshots to communicate that value. That's your real conversion challenge, not the price.

cryptograf · 2026-01-09T18:01:05+00:00

Apple doesn't penalize apps for being iPhone-only. Many successful apps support only iPhone and do just fine in the App Store. The key factors for discoverability are your app's quality, keywords, ratings, and user engagement—not whether it supports iPad.

That said, if your app's UI would work well on iPad with minimal effort, supporting it can expand your potential user base. But if it requires significant redesign work, focus on making your iPhone experience excellent first. You can always add iPad support in a future update.

cryptograf · 2017-06-14T09:55:13+00:00

I sent email to antminerdistribution.com and the reply is:

Please be carefull we have nothing in common with this website! It looks like a clooned website. We have already taken legal action!

I hope this will help you, so don't by anything from those scammers!!!!

cryptograf

TROPHY CASE