Help

Re: NEW: interface designer

3055 0
cancel
Showing results for 
Search instead for 
Did you mean: 

Whaaaaat?! :open_mouth:

image

18 Replies 18

You can trigger automations from an interface with data changes, the same as you would from a grid view or a portal. This is what I have done in my videos. However, with the limits of 25 automations and 50K runs, this method has scalability issues. Native support for locally run scripts/automations/actions from an interface without limits would be great but does not exist yet.

One of the design issues with running scripts from an interface is that many scripts need a place for input/output. That involves complex design choices that Airtable did not want to tackle in this first release.

Good to know.

Perhaps it goes without asking but can you modify the data in an Interface using script blocks or script actions, or custom apps that are operating completely external to the Interface itself?

Interfaces currently have no access to Scripting app. They currently have no access to any apps, custom or otherwise. However, the interface does reflect data changes created outside of the interface, although there are a few update bugs that I experienced in my video when I had to force a refresh to see changes.

That’s not the question.

Bingo - that’s the question. Circling back to @Faculty_Scheduling, there should be few issues – if any – to using script to effectuate influences upon Interfaces as I mentioned here.

Thanks for the answer. Yea that makes sense that some scripts can still run to effect change based on the data from records.

I guess for me I was thinking more about the input/output being on the interface so that we could create custom ways to view the data if that makes sense.

Yes, I noticed that too and it has dampened my initial excitement about Interfaces a little. I am still excited and totally understand that this is a feature right now that is only two days old. But at the moment, Interfaces looks to me almost like another app with a specialized function — say, an interactive version of the Page Designer — rather than being a comprehensive replacement for Softr or Stacker or even MiniExtensions. The great thing about those third-party apps has been and still is that they allow the developer (me) to keep end-users completely out of Airtable.

I find that my enthusiasm for Interfaces has actually grown over the past
couple of days. The current feature set makes implementing some functionality
more challenging than I would like, but the I find the possibilities even greater
today than I did two days ago.

A comprehensive replacement for a portal system requires an overhaul of the pricing model.
I do not expect such a system from Airtable without a pricing redesign.

Security is always an issue. Given that Airtable’s emphasis is on larger business, as stated in this interview, Airtable is undoubtedly hard at work on improving security/permissions. I expect that they have been working on it for a while. Over a year ago, I noticed that Airtable was looking to hire people who specialize in security. I suspect that they found great people who have been hard at work at this very complex issue.

I got this answer:

We do hope to develop ways to share Interfaces externally, but we’re just not quite there yet in the beta!

And I have been thrilled by the very recent improvements in control over sharing privileges. That change — just a month or two ago — has finally allowed me to go forward with some projects that previously I just couldn’t do in good conscience.

And I’m encouraged by your enthusiasm for the Interface Designer. You’ve spent more time with it than I but I hope to dig into it more deeply soon.

William