@bentoj72
Yes you can use native app features on any bubble page. Feel free to try it out using the demo app’s preview mode.
The bdk native plugin is a component of the bdk native apps service. It is not meant to work with any 3rd party app wrapping service.
Here’s a more detailed explanation of why the plugin is made available even without purchasing the bdk native apps service
okey.thank you.
i have a suggestion:
your native app capability is great. could you please make any demo video of making a native app from scratch(from bubble to appstore/playstore). it will be more understanding. in my case bdk native app feature are like a fog 
i think an example video will be more than enough for getting more about bdk native app features.
Thank you.
Hey @gaurav , thanks for keeping this amazing plugin update. I am almost ready to star using it. I just have same only request I did some time ago, the possibility of using touch id/face id in the app. For me it’s a must and I believe it’s not a difficult tool to develop as you already have on device storage, once this is working I won’t hesitate on move my mobile app from Dropsource to BDK Native.
Some questions, once I purchase the plugin, the source code you provide it’s only for one of tho OS, iOS or Android? Both? A discount on if we need both?
If I need to update my app, do I need to purchase it again?
Thank you so much.
Thanks for the feedback @bentoj72!
I actually was planning to make the demo app itself visible publicly so that anyone can see the bubble editor setup of native feature demos at BDK Native . But it turns only entire bubble apps can be made public and not specific pages. I’ll look into alternative solutions for making it easier to understand 
Meanwhile, all the features are covered in the native apps documentation with screenshots in respective ‘Example setup’ section of each feature. Hope that helps ease things a bit!
Hi @caeroa,
Thanks for the feedback!
So I did look into this a couple of weeks ago. But even before proceeding I found a logical problem actually - let’s say I’m able to authenticate a user using touch ID / face ID. Now, how do ‘transfer the login’ to bubble?
Bubble has its own authentication system, and per bubble’s provided workflows you can’t login as a specific user without knowing both their email and password. Obviously you wouldn’t want to store a user’s password on device. I’m curious as to how you achieve this on dropsource actually!
Simply ‘start a project’ at BDK Native. In your project page that opens up, you’ll see answers to these questions and other FAQs on what’s provided, original build and rebuild pricing 
Could you use a token to pass to bubble once face/print id? and then store that? like an OAuth? Don’t even know if bubble has that option, just thinking outloud 
Hey @gaurav, thank you for reply.
Actually the way touch id/face id is similar how the passwords managers work, the credentials are stored on the device (the password at least, the email is supposed to be shown always by the app once you type it the first time), Dropsource has the option of use the Keychain as storage so you can store the password there in an encrypted way, so you have to ente the credential once and then when you enter the app again you use your finger or watch at the screen, the app retrieve the password from where it was saved. I do not know if you have the options of save and read onto the keychain, if not, should be an option to use the password saving it in the device and making it secure with a 2AF or instead, ask the password only once, always have the app logged in and create a sort of pin of 4 of 6 digits only for that device (the first time you log in in that device), which would be data to save and retrieve with the touch id/face id. I hope I made myself clear.
I already saw the pricing, so convenient! I just need the touch id/face id to start building it 
Cheers!
Version 1.6 Update, October 21, 2019. Release notes
‘ Support for bubble’s pitcure uploader and file uploader element ’
‘ Support for bubble’s current geoposition ’
To upgrade, simply navigate to your project page. If you haven’t started a BDK Native project yet, start one now
Documentation link
Try the feature in demo app
Cheers,
Gaurav
Hey @gaurav anything new on this?
Cheers!
Hi @caeroa,
Not yet. So many things to do and so little time 
Wow, just learned about BDK, very impressive. Price is a bit steep for me but the feature list is stunning.
Q: is it or will it be possible in the future to store data on the device for offline access or just for faster caching? I have a long list with pictures and need to divide it into segments. Would love to have one long list with lazyload but cached on the device for fast loading after first time.
Q: Do i Understand correctly that the native functionality can only be used in a mobile and will not work in a browser right? That means two versions of the app?
Thank you for clarifying.
Master @gaurav,
We are having a lot of issues with our current wrapper no longer obtaining player Id’s from Onesignal for android devices, still working fine for Apple. Is this currently working for the BDK Native wrapper?
Any hot tips?
Hi @rico,
I’m planning to make things faster by including caching. But offline access / image storage from the bubble app is lot more trickier. I am planning on a native image list display template btw, which should be able to lazy load images with just the links
Not really. I use the same app for browser and mobile. The native functionality is ignored on browser.
For example let’s say you want to
All you need is simply add the BN - Native popup workflow step there. When opened in browser, this step is automatically ignored. And you add your show bubble popup step after that with the condition ‘appinfo’s is native is yes / no’. That’s it
In the demo app (BDK Native), I use this same technique. If you try a feature on your browser, I show you a small popup in my bubble app asking you to install the native app. If you press the same button inside native app it actually runs the feature
Just to make sure I understand, are you having issues with BDK Native Android app? I tried on my end and everything seems to be working perfectly fine in terms of getting player IDs, push notifications etc.
That all sounds really good. Shame I did not find you earlier :). Will use it for my v2 build for sure. Thanks gaurav.
To be clear, the issues we are having are NOT with the NOT BDK Native
It is with another notable wrapping service. However, we have been told by the service that android has deprecated support for certain view types and we want to make sure this is not an issue with BDK before jumping over.
Glad to hear!!
Yep I haven’t had any issue or any customer complaints regarding such a thing Welcome onboard!
Just want to share with you all my app published on Apple and Google - converted from Bubble using the BDK native service and plugin. It went live last month (Nov 2019).
I had a great experience using BDK and recommend it highly. The test app is really fantastic - one of the best aspects of this method. You can simulate the native experience on both platforms before you submit to the stores.
Check out my app!
Hello folks,
Here are two threads that I just added for all of you to check out!
http://forum.bubble.io/t/bdk-native-an-update/73391
Cheers,
Gaurav
HI everybody !
Just wanted to share with you that using BDK was a great success for us, the alpha version of the android app on google play took 3 days to be published (but it was my first roll out ever) and the production release (the real one!) was published in only 10 minutes!
Even more impressive, Apple took less than 3 hours to approve and publish my app!
Im still improving some stuff now but Gaurav will put the app on the Gallery thread next week if you want to check it out.
Big thanks to Gaurav for all his help and reactivity!
We got here an amazing and very accessible tool for all Bubblers who want to go native!
