@madw thank you!! Let us know if you have any particular features you'd like to see supported.

@eonpilot - Great question. We're starting with web, allowing people to authenticate users or accept payments from any link. From there, a user can download an iOS app and log into their account (which may already have an active subscription attached to it from web checkout). With our cross-platform native SDK, a user who is converted for the first time within an iOS app would include the 15-30% Apple tax. We'll be sure to stay compliant with Apple and Google as it's most efficient for merchants to convert end users at the point of highest intent - which is often inside of an iOS app.

@brooke_o_brien Thanks for the support!

@andrew_w_bass Thanks Andrew!

@soheil_hm thanks for following!

@michael_dawant1 Thanks Michael! Sounds like the future SDK would be the best way to integrate the two - we'd love to keep in touch and let you know once it is ready.

@srprs thanks! Excited for you to try it out soon.

@sean_jackson5 Thanks for checking Velvet out Sean! We're still early on the SDK front (dog-fooding it with the hosted pages experience we're launching) and would love to hear the pain points you've had in the subscription app space in the past so we can be sure we're building in the right direction for your needs. The foundation is andAPI that any client can consume. We'll be building better developer experience via SDK client libraries as we go, and early partners needs are going to shape a lot of that roadmap. Swift/Kotlin/React Native/Web are all things we want to tackle so Velvet can be fully cross-platform. Yes - we're talking a lot about auth and payments today but that's just a slice of what Velvet can do. We want to help customers with growth via customer acquisition, revenue expansion, reducing churn, etc. A/B testing different offerings helps with that mission for sure. Please reach out if you'd like to dive in deeper - would be great to have an early partner that's experienced what's out there and knows what they need going forward.

@shubham_pratap thanks! Please let us know what you think!

@emmalawler24 quick question, after authentication is it possible to restrict users to access certain page on application if they have not paid, like a membership app? Also sdk will work on react js?

@emmalawler24 @shubham_pratap yes, we'll be providing controls to combine authentication with access-control permissions to certain content - memberships are a primary use case! A React client library is on the roadmap. Reach out if you'd like to discuss more implementation details so we can make sure we're building in the right direction for your needs.

@devezehugo - Hey! Yep, good question - we've done a ton of user research over the past year, and both of us have been building cross-platform app systems for the past 10 years. Over the coming months, we'll be partnering with early-access merchants to iterate on the SDK before offering it publicly. If you're interested, please reach out!

@kinsey_durham_grace thank you!! Let us know if there are any features you'd like to see supported.

@cristinaj856 - Great question, thanks. There are two types of solutions teams can use today - (1) app stores, (2) point solutions. The app stores are not cross-platform. Apple gives you auth, payment, and data tooling to build on top of, but they won't help you (or often allow you) sell on Android, web, or anywhere else. Point solutions can be implemented as part of an overall system, but they require investment and resources to connect as a cohesive system, often resulting in poorly designed systems that lead to drop-off, churn, and lost revenue. We're building the connective tissue to authenticate your acquired users, monetize your product, and understand metrics so you can put your most valuable resources toward creating differentiated value beyond the account and paywall.

@jatin_rana2 Thanks for following!

@amberly_hendel Thanks Amberly!

@colinmathews - thanks, really helpful feedback! For merchants, there will be a few different pricing tiers depending on what features you want to leverage. It's free to use our basic hosted checkout pages, with paid features like custom domains and access to the SDK. We're still early, so it's most important for us to find great teams to work with before we monetize too much. Happy to collaborate as an early design partner if you're interested! Makes sense on the hesitancy around lock-in. We'll make sure there's flexibility for merchants to offboard if needed, while still respecting user privacy and experience. If there are any features or concerns that seem highest priority related to this topic, please let us know.

@dan_lesser - Yep, great question. Our hosted checkout pages are a no-code way to create accounts for new users, identify returning users, and accept payments using Stripe. Once you want a native or cross-platform experience, your engineering team can use our SDK built on top of the exact same system. This means you'll never need to do an arduous migration or risk losing valuable customer data as you scale. The other major benefit for non-technical members of the team is the control you'll have over onboarding and retention once Velvet is integrated. You'll be able to change copy, experiment with pricing, view data, and manage users without the support of an engineer. Let me know if there are any features you're particularly interested in!