3 ms·
raises hand Going through the website it all sounds pretty great and for a smaller project that I had to integrate with Amplify I think I would reach for this.
by _fat_santa 4y ago
raises hand
Going through the website it all sounds pretty great and for a smaller project that I had to integrate with Amplify I think I would reach for this. The problem I have is that if you're not integrating with Amplify, it's just another UI framework.
Also this thing is heavy, 1.5mb minified and 391k gzipped [1]. Compare that to another heavy UI framework like MUI that is only 477k minified and 131k gzipped [2].
Overall if you're using it with Amplify then that would be a reason to reach for this. But if you are not using Amplify, it just doesn't seem like a good choice.
EDIT:
Ok after thinking about this some more and reading the docs it's actually pretty nice, does a ton of stuff like pagination and login for you. If your boss comes to you needing a hastily done business app and wants you to use AWS. By all means reach for this and Amplify because it will get the app looking 90% good enough for about 5% of the work. The problem with this framework is this is just about the only sound use case. If you're building outside Amplify/AWS, or you are building a more established app, you are going to want to have control over all the things that this framework does for you.
[1]: https://bundlephobia.com/package/@aws-amplify/ui-react@3.0.4 https://bundlephobia.com/package/@aws-amplify/ui-react@3.0.4
[2]: https://bundlephobia.com/package/@mui/material@5.8.7 https://bundlephobia.com/package/@mui/material@5.8.7