Noted, thank you. Given that one of the most common issues newbies face with Bubble is responsive design, I am certain the demand is there.
Time to start saving my favourites!
Another fantastic review/walkthrough by our very good friend @nocodechris
Thank you Chris
(English subtitles available)
Yet another phenomenal review/walkthrough by @calderaricaio
Thank you Caio
(English subtitles available)
Bravo guys. Frames is fantastic. Good variety out of the box, and even better, quite easy to manipulate to customize as needed in my basic testing. Of course, this sampling just leaves me wanting more! Other have said it already, but I’ll +1 on sidebar menus/dashboard and RG’s. Super, super cool. Well done.
Plenty more in the oven Jason, we’re only just getting started
One more update for any of you looking to try out Frames. I’ve experimented with some bubble templates, and what I REALLY commend the Frames team on is there is not a lot of bloat. Not only do the content blocks load/paste in really quickly, the PAGES load quickly compared to some other templating systems out there - and still look great too. I’m glad to see that performance has not been sacrificed for design (at least not in my initial tests).
Just in case anyone missed it, a few RG’s can be found under “Lists” toward the end of the category listing. They’re really nice and huge time savers. And James isn’t even warmed up.
Amazing tool. Thank you very much for the time and thoughts that went into that plugin.
I have just watched https://www.youtube.com/watch?v=2N8LTaIThvQ&t=2435s.
It helped me tremendously to understand how to attack the responsive design in Bubble. Thank you for that Gregory.
I used one of the footers from Frames and got a notification that Frames is using 960px as a “default” index width. Changed the index width to 960 (3x320 breakpoints) and then naturally had to redesign the whole page including navigation, hero and main content sections of the page.
I noticed that the 2 containers in the Footer 11, mainly the outer and inner containers are using the following Maximum width (% of the current width):
Outer container:
Inner container:
I wonder if you would help me understand the following:
Does that mean I should also use the following structure (outer 150%-> inner 125% → content containers 50% up to 99% - depending on the needs) for the rest of my page?
Thanks for the advice!
Dom
Hey Dom and thanks for your kind words.
All responsive logic is baked in so I would simply keep the outer ‘parent’ group at 150% whilst retaining the inner ‘child’ group at 125%. Content containers therefor play ball and never fall out of sync.
Pixel perfect Bubble apps, every time
Reach out if you need anymore help/clarification.
Hey jameore,
you are welcome.
The components from Frames work out of the box - it’s really a time-saver!
I will try to keep the same parent-child structure for the rest of the website including non-fames components, which I had before I started integrating Fames components.
Thanks Dom, our intention right from the off was simplicity and ease of use. Glad it’s saving you time and effort.
Non-frames components, that’s devils talk we’ll soon plug that gap.
Lot’s incoming, hold tight!
Thank you for your support.
You guys are hilarious. I literally just created my own signup and onboarding forms less than 24 hours before this was put out. Maybe I’ll just take the weekend off and see what comes out next? Who knows, maybe you’ll magically create my whole app and I won’t have to do anything except type in the text. Keep up the awesome stuff guys. Thank you.