Feature Idea: Rise 360 Custom Block, Responsive & Interactivity 🎨

Idea Summary

Rise 360's Custom Block now supports both responsive layout and interactivity, and both are genuinely useful additions.

In my experience using them, though, neither is quite there yet: responsive containers only handle simple row or column reflow, and interactivity has to be hand built from scratch with no object library to draw on.

I'd love to see both gaps closed so Custom Block can hold up as a real page builder within Rise 360, not just a container for embedded objects. 🚀

One idea that might get there faster: bring over some of what already works well in Storyline, rather than building the same capability again from zero!

The problem 👀

I built a full course on Rise 360's new Responsive Custom Blocks Labs feature and used it hands on across a real project. Two gaps stood out to me.

First, the responsive containers only support row or column direction. There's no wrap or true grid behavior, so anything beyond a simple stack means manually nesting containers per breakpoint and hoping the reflow holds up. It works, but it feels more like a workaround than a layout system.

Second, now that interactivity has been added to Custom Blocks, it's a genuinely useful step forward, but it's also complex to build from a blank canvas. Every trigger, state, and interactive element has to be assembled from scratch, in a tool that doesn't yet have much of an object library or toolbar to lean on.

A few ideas that might help 💡

More flexible responsive layout. Wrap and grid behavior for containers, and a way to resize and reposition items per breakpoint visually (laptop, tablet portrait, tablet landscape, mobile portrait), would go a long way beyond just row or column reflow. That's what would make a block feel genuinely responsive rather than stacked differently on smaller screens.

A small object library for interactivity. Buttons, sliders, dials, hotspots, inputs, and markers as drag in components would mean interactivity doesn't have to mean recreating basic UI elements in custom HTML, CSS, and JavaScript every time.

Triggers instead of code. An on click, on hover, on state change trigger system could give Rise 360's Custom Block a logic layer that doesn't require a developer's toolkit to use.

Why I keep coming back to Storyline 🙌

Storyline already has a toolbar that covers a lot of this ground: insertable interactive objects, a trigger system, states, and per view object handling. It's not a rough sketch, it's something that's already shipped and well tested.

Leaning on it could help Custom Block get to a more capable place faster, without having to solve problems Storyline has already worked through.

It might also mean anyone who already builds in Storyline could pick up Custom Block more easily, with one mental model instead of two, and a bit less custom code overall since some of what people currently hand build in Code Blocks would already exist natively.

Supporting mockup 📱💻

Below are five screen mockup showing a real Rise 360 Custom Block (a "Listening to Understand" activity with card content and a branching call simulation) reflowing across laptop, tablet portrait, tablet landscape, and mobile portrait views, with a Storyline style toolbar added to the top of the Custom Block editor and drag to resize handles shown on each item. Just meant to illustrate the idea, not a literal spec.