Brad Tilton

2 minute read

We recently announced our new a low-code visual app environment for creators of varying skill levels called App Engine Studio. App Engine Studio allows you to build an app from scratch or from a template, and:

  • Innovate quickly - Create business-critical workflow apps in a complete low-code experience.
  • Delight your users - Convert ideas into superior end-user experiences across all the moments that matter.
  • Scale without sprawl - Unite business and IT with collaboration, reuse, and guardrails for enterprise-class support.

We covered AES in a [previous blog]() so in this one we’re going to focus on how AES can help you spin up portal and workspace experiences quickly in a couple of easy steps.

Add an Experience from AES

If you’ve created an application from scratch in AES, it won’t have any experiences by default, but you can add the following types of experiences:

  • Workspace
  • Portal
  • Mobile
  • Catalog

If you add a portal or workspace experience, you’ll get the following:

  • Experience record with the appropriate app shell applied.
  • A number of pre-configured pages complete with components, data resources, client state parameters, client scripts, and more.
  • Themes that are applied to the experiences.
  • For portals, a header and menu are created and applied to the portal experience.

In the following video, I walk through creating portal and workspace experiences through App Engine Studio.

The rough steps we took in the video are:

  1. Start from an AES app with at least one table extended from task.
  2. Create and explore a portal experience
  3. Create and explore a workspace experience.

More Resources

I would also take a look at the Creating a Configurable Workspace in App Engine Studio post from Developer MVP Ashley Snyder where she specifically explores adding a workspace to AES.

Make sure to check out the previous posts in this UI Builder series, and stay tuned for more posts.

Have a UI Builder topic you’d like me to hit in a future post? Let me know on Twitter, LinkedIn, or sndevs.com slack (@btilton).


Comments