How can you authenticate your app users who signed up for the app OUTSIDE of bubble?
Our users can register for app access (aka membership) via our website (hosted by wix). They then download the app to input their details to access the app content.
My current developer does not know how we can authenticate to where when someone registers (pays), & creates a username/password it, Bubble will know & allow them access to features in the app.
The reason we have this extra process is because we rely heavily on an affiliate strategy to sell our application & this is the easiest way to manage tracking with our affiliate software.
Seems like you’d have Wix send a API post to Bubble informing it that this user has a valid subscription. You obv can’t send the password but will can ask bubble for a magic link and use it to redirect the user to their account in bubble already logged in.
That being said it seems like integrating bubble with your affiliate sw would be a much easier and longer term solution
Makes a lot of sense & I appreciate you for your response!
I’d like to keep things simple as much as possible & utilize your suggestion of integrating the software with bubble. The only thing is we cannot understand is payment. If purchased through the appstore, we cannot accurately track our users that affiliates send to us. So we then planned to create a webpage for the registration so they pay for the app on it & then download the app to access. I don’t know what I don’t know & in this case, if you have some insight about this, I’m very open to it.
That should be possible by sending parameters or triggering events on the post payment page. Is this iOS only or Android too?
Also, I assume you are you aware of your active subscriptions somehow; whenever there’s a new one, you can trigger a conversion for that user’s affiliate (stored when the user signs up).
Definitely not an ideal situation, but if you decide to continue this route, the registration page can (and should, for efficiency and integration purposes) be in Bubble.
Note: requiring payment to download an app hurts conversions as a non paid user can be notified with push notifications if they have the app on their phone (and I assume there’s some science behind seeing the app occasionally on their phone + having downloaded it = more likely to pay but that’s pure conjecture).
The app will be available in both IOS & Andriod - full transparency, this workaround was created to avoid paying out double fees (affilaite +appstore payment processing).
I agree with you 100%, I’ve just now learned that as the app is being built, a website version is created at the same time - just have to reorganize the sizing to meet the different sizes. With that being said, I found that our affiliate tracking software can integrate. As you mentioned that is the BEST long term solution.
This app offers a free 3 day trial before accessing the content. It mimics mindvalley’s set up meaning that there is no free content offered & you have to be a member in order to consume it.
Understood, still I’m sure there’s plenty of dropoff of users between entering their contact info and starting the 3-day trial. Allowing for an app download prepayment (even without being charged) will likely help you recapture those who dropped off.
This is excellent counsel thank you. I’ve not seen this in application but surely open to it. Do you have any examples? My goal is to capture as much data as possible on the front end beyond our pixel.
IDK your flow and am not sure I get your question but just send users to the app and let them signup/onboard. If you have pixel data transfer issues, those are resolvable but even easier is to grab user’s email and password and signs the user up and store pixel and then give users a link to the app to continue onboarding
Appstore>register for an account> begin free trial > continue to feature access
Affiliate> sales page> bubble
Pixel will be installed within wix (sales page) & on Bubble.
Would you have any insight as to how to prevent having a PWA in this instance? I’m looking for a solution where users can access a sales page, which will redirect them to Bubble for processing payments, after which they can create a username and password. Some users will download and pay for the app through the app store, while others will visit the sales page to become members.
Currently, our app workflow follows: splash screen > register > start free trial. My developer suggested that we might need to create separate apps for this. Is there a workaround that would allow us to achieve this without creating a Progressive Web App (PWA) or a completely separate app? We want to streamline the user experience and make it as seamless as possible.
Because we have affiliates, I need them their traffic sent to a webpage to track.
Then we also will be in the appstore & people can sign up for the app there.
Instead of going the webhook route, we will create a sales page with a button leading to bubble to pay.
Does this make more sense? because I don’t fully understand it is challenging to explain. I know what it is that we’re trying to achieve though.
Not following but e/t should be in Bubble which can be accessed as a app or a webpage. I’d suggest you and your dev collab on a workflow diagram before anything is done and once you approve he/she should be able to execute.
