Hey guys so i often see people asking about Dropsource when they’re thinking of going truely native.
I just saw Dropsource will be having a webinar next week and I think it will be perfect for anyone who wants to know more about Dropsource.
Dropsource and Bubble works really well together as long as you’re lucky not to hit any of the current dropsource limitations.
So will be nice to check it out. See link below.
FYI I’m in no way associated with Dropsource. I’ve just been answering a lot of dropsouce questions on this forum because of my experience with Dropsource and i thought this will answer a lot of peoples questions better.
Here is the call
Curious what you can expect from the Live Demo? Join Wade Sellers, our Developer Support Specialist, as he walks through the ease of using the Dropsource Platform. He will discuss
Anyone that also hangs out on the Dropsource forum will know that @seanhoots does not just have Bubble ninja skills, but Dropsource too. And he’s also very generous with his support over there.
Cheers guys, I will definitely pass on that request and if we have a recording link we’ll be sure to share it…
And yes @seanhoots is by far our most active and helpful community member over at the Dropsource forum, pretty sure he’s figured out more than most of us within the team have about the capabilities of the software lol - we are incredibly lucky to have him contributing to our ecosystem…!
I can’t speak about all background actions but I can confirm that music can continue playing when tha dropsource app is in the background.
One thing though i realized which i never got to find out why was that when the music is playing in the background and you start another music in a different app it still continue to play. So you basically have two music playing at a time.
I’m not sure if i was doing something wrong.
In any case I will suggest people to ask all these dropsource questions in the dropsource forum where you’re likely to get more response from other users and the dropsource team.
Am I understanding that essentially if I want to build only a native mobile app (no desktop/web app) then I should just use Dropsource instead?
But if I want both a mobile app and a native mobile app I can build my app in Bubble and then use Dropsource to make it native mobile (ie no rebuild required?)?
Just want to check I’m understanding what we’re talking about here cause I’ve been down a few rabbit holes now! Thanks!
Kate
If you use Bubble to build a mobile app, you are not building a native mobile app. You are building a web app, that gets packaged up in a wrapper, that can be deployed to a store.
If you use Dropsource to build a mobile app, you are building a native mobile app. It is possible to build a web app for laptops and desktops using Bubble, then use the logic and brains from that web app to power a native mobile app built in Dropsource.
That is definitely not the recommended use for Dropsource, otherwise you’re just building another non-native app. I would highly recommend using the native components and rebuilding the frontend of the app in Dropsource, NOT using the webview.
@scottb50 you’re right but someone might misinterprete what you said to mean that dropsource is just an app wrapper.
To make things clearer i will say it this way.
Dropsource allows you to create a native mobile app which is powered by a bubble backend (database + api workflows for some application logic).
In addition dropsource has a webview element that you can use to wrap your bubble web application as a mobile app that can be published on the app stores.
Also you can even build a hybrid of the two. That is create your app as a native app as with dropsource native elements and mix it up with some webview components for some pages from bubble. This can be tricky though as its not simple to share data between the native pages and the webview pages.
I’ve saved a lot. I used to have 4 Android developers to work on the project and because of dropsource I could sleep quietly. I used firebase for backend before. Now no longer, bubble and dropsource saved me.
