I’m thinking to write an e-book/guide called Complete Guide on How to Build Chrome Extensions and Website Widgets in Bubble
Basically I would explain (step-by-step) how I implemented Heyhi overcoming all the tech limitations that Bubble has when it comes to:
Loading a Bubble app in an iFrame embedded in a website with a script added in the HTML Header of the website;
Handling communication between an iFrame and a Bubble App;
Performing cross-origin REST Api calls from the Bubble app loaded within the iFrame;
Sending Javascript callbacks data to the Bubble app;
Managing cookies (cross-origin);
EXTRA access to a project with Reusable Components like: Payment module (with Stripe), Basic Admin Page, Basic responsive Landing Page;
Are you interested in this guide? IF YES: what would you love to see in the book? IF NO: what’s the first tech challenge do you face while using Bubble?
I’ve been holding off on some projects because of the browsers crusade to remove cross origin cookies/ Iframe elements.
I keep seeing “jwt authentication” as the next progression. So my concern is building out these only to have Chrome push an update which kills it overnight. Is this related or do I have my wires crossed?
Additionally, my interests would be with the widgets like having a chat button more than the Chrome Extensions but I’m sure I would be open to looking into both at some point!
an example of a simple chrome extension.
e.g. a copy of pin to pinterest which saves a site to your bubble database (e.g. a field type text underneath a thing called “websites” created everytime you press “pin to site”).
Creating Chrome extensions via WebDGap is fairly easy, but getting that extension to have access to the “browser data” (i.e. what is the currently open tab) would be amazing.
I’d 100% buy this… why don’t you test the market and create a quick live event, or video explaining the basics and offer a discounted prepayment option to fund its creation.