<story><title>AWS Amplify Studio: Figma design to full-stack apps</title><url>https://aws.amazon.com/about-aws/whats-new/2021/12/aws-amplify-studio/</url></story><parent_chain><item><author>eunoia</author><text>I was working heavily with amplify a couple years ago and to be honest it was an awful experience.&lt;p&gt;Common use cases weren’t handled well, deployment failures were common, overall architecture was actually less coherent when using amplify than just the constituent AWS services directly, etc…&lt;p&gt;It felt like a kitchen sink of functionality that no one was incentivized to actually make work well together.&lt;p&gt;Have things improved?</text></item></parent_chain><comment><author>0xB31B1B</author><text>My team (5 engineers, 18 months building so far) currently runs the largest amplify based project in terms of number of resources used. We have a direct connection to the core team and their support has been great. Things were quite rough until about 6 month ago. The new releases in version 7.5.x unwind a ton of technical debt that caused serious instability. If I were to start our project over again knowing what I know now I might use SAM or the serverless framework instead of amplify, but I am not sure. The graphQL spec definition to dynamo table feature is the entirety of the magic in amplify IMO, and it has seriously sped up our development time. I strongly recommend against using any of the UI components, or many of the features that appear to be &amp;quot;tacked on the side&amp;quot; because in my experience they are tacked on and don&amp;#x27;t work well. Happy to answer any questions.</text></comment>
<story><title>AWS Amplify Studio: Figma design to full-stack apps</title><url>https://aws.amazon.com/about-aws/whats-new/2021/12/aws-amplify-studio/</url></story><parent_chain><item><author>eunoia</author><text>I was working heavily with amplify a couple years ago and to be honest it was an awful experience.&lt;p&gt;Common use cases weren’t handled well, deployment failures were common, overall architecture was actually less coherent when using amplify than just the constituent AWS services directly, etc…&lt;p&gt;It felt like a kitchen sink of functionality that no one was incentivized to actually make work well together.&lt;p&gt;Have things improved?</text></item></parent_chain><comment><author>IceDane</author><text>Wow, this is the &lt;i&gt;exact&lt;/i&gt; experience I had.&lt;p&gt;Not only were all the issues you mentioned common, but the quality of their libraries(JS in my case) were just horrendous. At one point there was a run time crash in their blob storage library whenever you listed an empty bucket. I tracked the root cause down to one of their devs intentionally casting away type information(`as any` in typescript) and thus not realizing there were more cases than they were handling. This somehow passed code review and testing and was published.&lt;p&gt;It was absolutely horrendous. We barely moved a millimeter because we were constantly slowed down by their tooling. I wrote a very long issue about this and just got some community representative who assured me who would do &amp;lt;a series of vague, non-committal promises&amp;gt;.&lt;p&gt;Shortly thereafter we changed to GCP and Firebase and we were at feature parity in no time and moving fast after that.</text></comment>