AWS Amplify could improve by offering more flexibility in complex enterprise scenarios. For example, when you need advanced custom authentication flows or fine-grained access control, it can be limiting. Also, some debugging around auto-generated resources could be clearer. Another area is deeper integration with existing infrastructure as code, so larger teams can blend it into broader pipelines more seamlessly. One pain point I have is when I outgrow the default patterns in AWS Amplify. As apps scale, having more granular control over back-end infrastructure, like custom VPC setups or complex network configurations, is not as straightforward. I would love to see tighter integration with CloudFormation or CDK for smoother transitions when custom infrastructure is needed. Also, improved visibility and debugging of AWS Amplify-generated resources would be welcome. A smaller improvement I would love to see in AWS Amplify is more intuitive error handling during deployments. Sometimes AWS Amplify deployments fail without clear messaging, especially with build configurations. Better visibility into detailed logs would help. Also, more built-in CI/CD customization options for multi-stage environments would be a welcome addition.
Currently, I do not believe that AWS Amplify is lacking in features, but one of the main limitations I feel is a lack of flexibility in CI/CD pipelines. The built-in pipeline works well for simple front-end deployment but becomes restrictive when I need custom workflows, multi-stage approvals, or integration with other AWS services. This is one area that AWS could improve.
Software Engineer at Network Intelligence (I) Pvt. Ltd.
Real User
Top 5
Sep 17, 2024
The documentation needs improvement, as it is not user-friendly and can be challenging for novices. Furthermore, the AWS user interface could be improved. Although AWS is making improvements, there are other solutions, such as Clerk, that provide a more streamlined and less expensive service than Cognito.
I don't think there are major issues, but there is room for improvement in the UI/UX of AWS Amplify. The UI still needs to be more polished and user-friendly. It's currently a bit like drag-and-drop initially, but there should be more options to customize the UI based on our needs.
AWS can implement multiple web applications, and cross-platform applications, like iOS (AWS currently supports Android). They have Node.js, but they can also maybe integrate with cross-platform functionalities.
Its capability to handle big projects needs to be improved. If you generate a user interface in Figma and import everything where all components are in one directory, currently, it is complicated. It isn't able to cope with that. For small projects, it is not an issue, but if you have big projects and you want to use AWS Amplify, then it gets more difficult. That is the most important point for me. It should be improved to cope better with bigger projects.
AWS Amplify revolutionizes app development with tools for real-time data syncing, cloud service integration, and simplified CI/CD processes, making it ideal for rapid deployment of mobile and web apps.Developers find AWS Amplify invaluable for its ability to simplify application growth and management. It offers seamless cloud service connections and integrates with tools like Figma, enhancing usability and productivity. Challenges include limitations in enterprise scenario flexibility,...
AWS Amplify could improve by offering more flexibility in complex enterprise scenarios. For example, when you need advanced custom authentication flows or fine-grained access control, it can be limiting. Also, some debugging around auto-generated resources could be clearer. Another area is deeper integration with existing infrastructure as code, so larger teams can blend it into broader pipelines more seamlessly. One pain point I have is when I outgrow the default patterns in AWS Amplify. As apps scale, having more granular control over back-end infrastructure, like custom VPC setups or complex network configurations, is not as straightforward. I would love to see tighter integration with CloudFormation or CDK for smoother transitions when custom infrastructure is needed. Also, improved visibility and debugging of AWS Amplify-generated resources would be welcome. A smaller improvement I would love to see in AWS Amplify is more intuitive error handling during deployments. Sometimes AWS Amplify deployments fail without clear messaging, especially with build configurations. Better visibility into detailed logs would help. Also, more built-in CI/CD customization options for multi-stage environments would be a welcome addition.
Currently, I do not believe that AWS Amplify is lacking in features, but one of the main limitations I feel is a lack of flexibility in CI/CD pipelines. The built-in pipeline works well for simple front-end deployment but becomes restrictive when I need custom workflows, multi-stage approvals, or integration with other AWS services. This is one area that AWS could improve.
AWS Amplify can be improved in some areas, particularly in providing more robust documentation and easier customization options.
The documentation needs improvement, as it is not user-friendly and can be challenging for novices. Furthermore, the AWS user interface could be improved. Although AWS is making improvements, there are other solutions, such as Clerk, that provide a more streamlined and less expensive service than Cognito.
I don't think there are major issues, but there is room for improvement in the UI/UX of AWS Amplify. The UI still needs to be more polished and user-friendly. It's currently a bit like drag-and-drop initially, but there should be more options to customize the UI based on our needs.
AWS can implement multiple web applications, and cross-platform applications, like iOS (AWS currently supports Android). They have Node.js, but they can also maybe integrate with cross-platform functionalities.
AWS Amplify could improve in the deployment. It would be beneficial to have more methods, such as automation.
Its capability to handle big projects needs to be improved. If you generate a user interface in Figma and import everything where all components are in one directory, currently, it is complicated. It isn't able to cope with that. For small projects, it is not an issue, but if you have big projects and you want to use AWS Amplify, then it gets more difficult. That is the most important point for me. It should be improved to cope better with bigger projects.