In general, I haven't had good experiences with Amplify in the past. A lot of those frustrations are probably better directed at the Cognito and Pinpoint teams

In general, I haven't had good experiences with Amplify in the past. A lot of those frustrations are probably better directed at the Cognito and Pinpoint teams specifically. Amplify's been one of those things that worked amazing for demos and POCs, but was super frustrating to tune for actual production needs. One magical moment for me was the way it would spin up a copy of the entire stack (frontend and backend) for each pull request and tear it down on close, all with basically zero configuration needed. Of course, if you had OAuth or other things that required certain domains and whatnot, it broke, but the promise was there. However, this past month had a lot of interesting launches from the Amplify org. You can now use Amplify from CDK, override the settings on the resources it generates, and even tie it into a CDK pipeline. There's a streamlined GraphQL transformer so that you can just write a GraphQL schema and get a Rails-like experience that generates a full working app for it, with integrations on DynamoDB and OpenSearch. https://aws.amazon.com/amplify/blog/?awsf.blog-post-types-filter=*all&awsf.blog-learning-levels-filter=*all&awsf.blog-master-mobile=*all https://aws.amazon.com/amplify/blog/?awsf.blog-post-types-fi... There's a lot to like here. I don't know if any of this would live up to the potential, but at least you can see that AWS is investing pretty heavily in it. I think Amplify has a real future as an alternative universe way of working with AWS for app building. I could see this studio launch being a quick way to prototype/iterate/experiment with designs before giving feedback back to a design team.