6 Reviews and Ratings
20 Reviews and Ratings
No answers on this topic
You should go for using it in particular if you are going to be build code once run everywhere kind of things and you want to not write most of the backend on your own. As AWS Amplify can take care of a lot of backend things for you and you can manage most of the stuff from front end coding. perfect for using in react/ flutter apps. Additionally better to use when you are going to use other AWS service and don't want to scatter things aroundIncentivized
When you want to display spreadsheet based reports, it's really convenient as it has everything out of the box.If you have very basic components like combo boxes or lists, there is hardly a point in using such a large component set.In the end, it's a matter of finding a good balance between functionality and complexity. Incentivized
UI and design of the AWS Amplify for easier setuppainless user flow for react, angular etceasier setup using CLI with effective questions.Incentivized
Handle large and complex datasets using its table widget (DataGrid)Handle large and complex hierarchical datasets using its tree table widget (TreeList)Customize widget to fulfill advanced requirements such as adding a complex grid inside a grid cellIncentivized
AWS Amplify init ends up changing the cloud. there should be deploy kind of thingconfusions between Front end backend as both codes get mixed. this should be kept separatebetter documentation with use casesIncentivized
Documentation could be improvedBetter examples of code in languages other than CBetter wizards for building applicationsIncentivized
Its AWS take on the Firebase kind of system for providing backend as a service. Although Firebase has advantage of bigger community, better documentation and code examples; AWS Amplify is creating its own space where you will be going to use AWS products and Infrastructure in your project. Amplify Dynamo DB and GraphQL have clear cut advantages that have no direct alternative in Firebase as real time db and firestore documents both lack versioning.Incentivized
DevExpress Universal controls are much simpler to use, implement and customized as compared to Kendo. Learning curve for telerik is high, though level of customization that can be achieved with telerik exceeds that of DevExpress Universal. Found DevExpress Universal community support to be better then its competitors. License cost is also a wining bar here.Incentivized
saves time on righting backend interfaceseasier to setup with react/ react nativelambda functions can be used to extend functionalityIncentivized
It is good for asp.net application and it takes less time in development which we used two years back.We have stopped with these tools when clients were asking applications to be built in angular or react. We have switched to Kendo.