Hey folks, the paradigm has shifted to fully embrace calling tasks from tasks as the nesting primitive. I suspect calling tasks from apps is also very much in scope. What about serving/deploying apps from apps? Hear me out: An admin app that serves as a landing page for onboarding users across an org. Has full cluster access, all projects/domains etc. New users hit that app and log in with their SSO. After auth, a project is created for that user and a secondary app, scoped to that project is deployed. All from the first app via the sdk with appropriate credentials. This could be a dashboard or notebook for example. From here they can exec tasks workflows and still peruse them from the regular console in a nice clean way. I'm experimenting with it now on devbox and hitting some limitations. I think they're mostly devbox limitations (e.g. an app doesn't have access to a local docker daemon for building and serving secondary app, this would be a non issue in prod with remote builder). There have been some thornier issues though that make me wonder if I'm abusing the feature. Handling admin in a regular ec2 instance would give a lot more flexibility but that's separate infra to manage. Thoughts?

You wouldn't use an app to create apps - this needs durability and error handling- so tasks is better

You wouldn’t use an app to create apps - this needs durability and error handling- so tasks is better

it’s possible, but as Ketan said a task would be better for this