Is it doing it server-side or client only?
they don't mention it explicitly in the video so i'm not sure. there is a part of the video where they walkthrough setting up a cloudflare worker for secure tokens on the client. so i'm guessing maybe client only. i don't use framer myself to check if there is a rendering toggle like webstudio.
for me, mostly the UX of the feature is what made me decide to share here. there are a lot of folk who don't have any experience with working with APIs. this feature seems like a good entry point.
from an ease of use perspective.
I think its not live yet, don't see content property on text
They didn't make it easy to work with APIs, it just looks easy on the demo where they used built-int demo apis
problem with REST APIs is that you don't know what api parameters to type and what data you get, you need to read the docs
and they are not solving that
there options to use their endpoint or to add your own
so for someone getting over the cold start part of learning how api works it seems like a start to me
adding your own endpoint is the only real option, others are just demo
and when you add your endpoint you are doing the same thing we do
you have to know ho to add it
more so I don't see how they allow you adding headers etc
that's why they suggest to wrap an api with a worker, because all secrets would be there
we are miles ahead of them here
we do basically most of that without requireing you to create a worker, because we already run it in a worker for you
so from your perspective having some default endpoints in the dropdown aren't helpful for folks coming from Webflow that haven't interacted with an API before?
its just a demo, its helpful in terms of educational purposes, but not practical
they basically added a few default apis to the dropdown before user has to enter a real api to play around
i didn't get the impression that their endpoint is only a demo and can't be used in production. where did you get that understanding from?
like it seems like if i just needed to use the location api for some basic content i could. i agree what webstudio has is more robust so i'm definitely not comparing the two from a funtionality perspective.
more from a beginner perspective coming from webflow where it' common for technical stuff to be abstracted away. thinking about a less abrupt transition for learning.
how the abstraction of css has helped folks starting out to get over the knoweledge gap but they eventually need to know how css works to get the most out of the tool.
I mean from practical point of view, weather data etc, is rarely needed
don't want to go into this discussion, but framer's approach isn't giving you full power, so its good for limited use caes and that's why its easier
webstudio is intentionally different
well if you ever have time to circle back i would love to get a better understanding of the intentional difference from a ux perspective.
i was more interested in your direct response to having select default endpoints as an option.
maybe i’m missing something here
i’m also fine if it’s not something you are interested in getting into. that’s why i said if you wanted to circle back if it made sense.
like I said its nice, especially for demo purposes
no need to continue the discussion.
