How to structure script-based tool dashboards for NEAR dApp interactions?

Development
1

Hi NEAR devs,

I’m currently building a script-based tool dashboard that interacts with NEAR dApps. The goal is to let users trigger actions, switch between tool panels, and load different script modules all without refreshing the page.

Before going further, I wanted to ask:

What’s the best approach for managing frequent script-triggered functions in NEAR dApps? Especially when the interface needs to be lightweight, modular, and responsive.

I’ve been experimenting with different layouts and script-handling flows. Here’s an example of the type of script interface I’m working with: script interface https:/fluxusteams.com

Any advice, patterns, or examples from your experience would be really helpful.

Thanks

4

Hey nice to meet you Ryan.

First, I should note; the best place to seek developer support is the Near Dev channel on Telegram (@neardev), and I encourage you to follow the builder broadcast channel for continued updates (@nearlegionbuilders).

This is an interesting ask… what are these script modules and where are they stored and being executed? Is this third party, untrusted code, or from a trusted, already deployed registry of scripts? Are they running on the client, or on a server?

I tried opening up your site, fluxusteams, but I get a “Account suspended” error.

I can’t really give much advice without understanding more, but find me on Telegram @ejlbraem and I’d be happy to talk about this more.

1 Like