šŸ’ŗ Introducing Bask: A VS Code extension for building plugins

Hello friends :slight_smile: @Sarah_Esteve invited me to speak at DevDay - the Bubble Conference for and by Bubblers taking place all day long today. I’m registered to give my talk on Omnisearch and Bask (a VS Code extension I made to make Omnisearch) from 3 to 4pm CST (in 6 minutes). If you’ve been on the fence about using Bask (or Omnisearch) or are just curious about ways to accelerate search / plugin development in Bubble, I invite you to tune in. Connection details below:

Links to resources I’ll be reviewing:

@zelus_pudding sorry, I’m not sure how to reach you differently. I have used Bask for a moment and then turned to other ventures, but the payments have still been going and I don’t see any way to cancel the subscription. Can you please cancel the subscription under @jachowicz.piotr ???

Hey Piotr! The way to unsubscribe is nearly the same as subscribing - log into your account at Scious | Plugins, then tap unsubscribe as shown below. I went ahead and just did this for you so you’re good to go - your subscription will not renew. Thank you for giving us a try!

You’re subscription is now cancelled:

Hey @zelus_pudding

Loving Bask. Would it be possible to add support for mobile native plugins?

Here is an example object to work with.
From what I could see in your extensions.js file, it should just be a matter of adding ELEMENT_RN_COMPONENT to the defined PLUGIN_FUNCTION_TYPES, right?

{
    "display": "QR Scanner",
    "property_applications": {
        "resizable": true,
        "MinWidth": true
    },
    "add_is_visible": true,
    "can_fit_height": true,
    "states": {
        "AAE": {
            "caption": "QR Result",
            "name": "qr_result",
            "value": "text",
            "initialization_code": {
                "fn": "function(properties, context) {\n\n\n\n}"
            }
        }
    },
    "events": {
        "AAF": {
            "caption": "On Scan",
            "name": "on_scan"
        }
    },
    "code": {
        "preview": {
            "fn": "function(instance, properties) {\n\n\n\n}"
        },
        "reset": {
            "fn": "function(instance, context) {\n\n\n\n}"
        },
        "rn_component": {
            "fn": "function(props) {\n\n\n\n};"
        }
    },
    "platform_type": "mobile"
}

I’m having a problem with server side actions… I create them in the plugin editor, but Bask Pull doesn’t create them in VS Code. Other changes I make in the plugin (e.g. elements) are syncing properly.

A great idea! Working with Bubble to make this a reality! Details to come :slight_smile:

Hey @lostsheep, I am looking into this issue and will follow up once I have a fix/additional detail :slight_smile:

Hey @zelus_pudding, could you point me in the right direction to find the receipts for my Bask subscription payments? Thanks!

Just sent those to you Jake!

hi @zelus_pudding !

Can bask create completely new actions from code side? or is it needed to create these in editor first, synch to repo and then you can work with them via bask?

thanks for this great tool!

Hi @zelus_pudding, I’ve been having problems getting Bask to connect to my Bubble plugins for a few days now.

Every time I run the Bask Switch command I get stuck on the ā€˜Bask is updating plugins list’ message:

Screenshot 2025-11-27 at 10.41.59

It’s feels like the authorization has expired, but there doesn’t seem to be any way to refresh it.

Anything I can do to get bask working again or troubleshoot the issue?

Thank you!
Alex

@zelus_pudding is usually very active and fast to respond both on the forum, DMS and emails too - however he’s not posted or been in communication for a long time now so I’m bit concerned. Does anyone know if he’s ok? :folded_hands:t2:

I chatted to him just before Xmas.

I am alive and well :slight_smile: I apologize for the painfully slow response times. Since I released Bask (and OmniSearch) years ago I have become a lot more focused on non-Bubble projects. I’ve essentially stopped releasing updates except for providing support to customers who pay for that extra support. The products still work fine for most people - I have customers who’ve been using my plugins in production for over three years… chugging along to this day.

As it pertains to Bask in particular - there are many new features customers have asked me to build/that I would love to build:

  • Multi-Bubble account compatibility
  • Bubble aware integration with LLMs to make plugin generation a breeze
  • Mobile Plugin Support

As it pertains to that last one, Bubble even reached out to me to make Bask compatible with the new Mobile Plugin editor - which I believe has been in alpha for nearly a year (or longer?). I would love to build these things but the revenue just isn’t there to justify spending more time developing Bask. When Bubble reached out to me, I thought about how I could justify continuing to develop this extension… and came up with a list of requests revolving around marketing support - to help me get the word out about Bask. To help me get sales.

In the end, it was not a priority for them to help me turn this into something anyone could use to make plugins - to exchange marketing support for my dev hours. They said they were focused on the release of the mobile product and to follow up later. I did but nothing came of it.

Without their support, this thing looks like it’s going the way of the Dodo. It’s too bad, because this product was amazing. But it could have been so much better. I’ve put so much time into it but have gotten so much more in return on other projects that I just can’t justify working on it anymore (again, except for customers who do pay for the additional support). There will be folks who can download it and use it without issue. And there will be others who experience issues - a lot of times in software dev, as am sure we all know too well, bugs can be machine or OS specific.

To those who continue to use it without issue - I’m excited for that. To those who cannot, they will cancel their subscriptions or simply not continue using this past the free trial. Your milage will vary. If someone or this community can get ahold of Bubble to give supporting this a second consideration, I’d be all ears for that. Otherwise, it was a deep pleasure to have made something a few here really enjoyed :heart:

It’s tough to make dev tools for Bubble pay off. I think that the only paths are:

  • lead gens for the agency, a la buildprint of @georgecollier
  • build it so that Bubble acquires it, a la Flusk or Deezign by @bek
  • …?

Why not open source Bask?


Alternatively, I’ve built a little CLI hack that I use to update my plugins: Tiny demo: Pled CLI tool for plugin development - #21 by rico.trevisan

I would have to detangle Bask somewhat from my main business to open source it. If one were to buy it, they can give it away for free if they really want to.