5 ms·

It is possible extensibility will be via Google Apps Script, about as close to "freeform" code one can get in a sandbox. Google have successfully implemented Ap

It is possible extensibility will be via Google Apps Script, about as close to "freeform" code one can get in a sandbox. Google have successfully implemented Apps Script in a number of G Suite products so I would be optimistic about seeing it in App Maker for advanced scenarios. Fingers crossed

tyingq 10y ago
Many of the tools I mentioned have scripting capabilities, but that doesn't keep you from hitting a wall, because you're scripting in whatever limited context they give you. Sometimes the wall is the data model, or the construct they give you for navigation, access control, roles, etc. Something like freeform javascript that executes in the client would help a lot, because you could patch around limitations in many cases.
- spankalee 10y ago
  Creator of App Maker here, though it's been a while since I was on the team. Smoothing out the transition from on-rails to off was one of the original design goals, so there was arbitrary server and client scripting from pretty early on, and a component model to create widgets. The project as moved from being hosted on App Engine to being hosted on Docs infrastructure, so I'm not sure what the specifics of extensibility are, but I suspect they're pretty good, but more Apps Script oriented. Should be a good solution for heavy Docs users. My thinking in this space is that you really can have your cake and eat it too with these tools, though it requires a really thought-out design, and that they built-in features use the same extension points that are available to users. With JavaScript available on the client and server it becomes less of an issue whether you can run code at all, and more of an issue of whether you can run at the right time and intercept the right flows. Especially with Web Components on the client pretty much taking care of components. Providing a standard router on the client and server with similar middleware and handlers, and also middleware/handlers on state changes, you can get close to easy to start with and fully extensible.
  - tyingq 10y ago
    Sounds promising. This is why HN is so great. Meaningful insider feedback in the space of an hour. Thanks for that. The other limiter is less technical. Finding a way to charge per user only for true internal users. That was my other stumbling block...tools that want to charge for everyone that touches a built app in any way whatsoever.
panarky 10y ago
Looks like App Maker already supports JavaScript for both server and client scripting, including bindings to read and write data. https://developers.google.com/appmaker/scripting/overview https://developers.google.com/appmaker/scripting/overview
- sitepodmatt 10y ago
  Oh sweet "Server scripts run on Apps Script. They can access databases directly and use Apps Script APIs like calendar, email, and more.".. This could be very interesting

tyingq 10y ago

Many of the tools I mentioned have scripting capabilities, but that doesn't keep you from hitting a wall, because you're scripting in whatever limited context they give you. Sometimes the wall is the data model, or the construct they give you for navigation, access control, roles, etc. Something like freeform javascript that executes in the client would help a lot, because you could patch around limitations in many cases.

spankalee 10y ago
Creator of App Maker here, though it's been a while since I was on the team. Smoothing out the transition from on-rails to off was one of the original design goals, so there was arbitrary server and client scripting from pretty early on, and a component model to create widgets. The project as moved from being hosted on App Engine to being hosted on Docs infrastructure, so I'm not sure what the specifics of extensibility are, but I suspect they're pretty good, but more Apps Script oriented. Should be a good solution for heavy Docs users. My thinking in this space is that you really can have your cake and eat it too with these tools, though it requires a really thought-out design, and that they built-in features use the same extension points that are available to users. With JavaScript available on the client and server it becomes less of an issue whether you can run code at all, and more of an issue of whether you can run at the right time and intercept the right flows. Especially with Web Components on the client pretty much taking care of components. Providing a standard router on the client and server with similar middleware and handlers, and also middleware/handlers on state changes, you can get close to easy to start with and fully extensible.
- tyingq 10y ago
  Sounds promising. This is why HN is so great. Meaningful insider feedback in the space of an hour. Thanks for that. The other limiter is less technical. Finding a way to charge per user only for true internal users. That was my other stumbling block...tools that want to charge for everyone that touches a built app in any way whatsoever.

panarky 10y ago

Looks like App Maker already supports JavaScript for both server and client scripting, including bindings to read and write data. https://developers.google.com/appmaker/scripting/overview https://developers.google.com/appmaker/scripting/overview

sitepodmatt 10y ago
Oh sweet "Server scripts run on Apps Script. They can access databases directly and use Apps Script APIs like calendar, email, and more.".. This could be very interesting