3 ms·

After getting burned by the dumpster fire that is Amazon Honeycode, I wouldn't touch this with a 10 foot pole.

by istjohn 5y ago

yanlezeiler 5y ago
What's wrong with Honeycode ?
- istjohn 5y ago
  1. There is no data export tool. The only way to pull data out is either to copy and paste from each and every table into Excel or Google Sheets and export from there to CSV or to roll your own custom export script using their poorly documented JS API. 2. Once you have more than 3,000 or so rows in a workbook, everything grinds to a crawl. It can literally take over a minute for any kind of data mutation in the administration user interface or in the app interface to be reflected in the display. This means that doing anything on the app becomes literally slower than if you were to do it with paper and pencil. And this is despite paying $20/month for the Plus tier, which purportedly allows 10,000 rows per workbook. 3. The project lacks polish and user-friendliness throughout. 4. It is buggy throughout, and developer updates have introduced new bugs multiple times. For example, recently the last record in a table started getting displayed in my app view even though it is excluded by the list filter in that view. 5. The bug reporting process is difficult to the point that I don't even bother anymore. 6. The first time you try to open an old workbook, it will error out. Presumably they are using serverless and the Lambda function is cold.
amzn-throw 5y ago
Amazon/AWS teams are so distributed and independent that it the quality of the output of one team very rarely reflects in any way on the quality of the output of another. This is almost always a good thing. There are of course centralizations and standardizations - the AWS SDK, Console UX, API guarantees, etc. But Honeycode has almost no relationship to the rest of AWS, technically, or organizationally.
- IceDane 5y ago
  Except what this really means is that nearly any part of AWS you have to deal with has been clobbered together by a series of different teams with little cohesion. The last time I dealt with AWS and amplify, this was glaringly obvious in several places. Settings pages where one tab looked and behaved radically different from the other. A seeming total lack of communication between teams resulting in badly synced package released with bugs due to version differences. Also frequent omissions in documentation requiring you to hunt it down in github repos or in totally different places(Say Amplify uses X to do something, you might have to find info for using X in an Amplify context in the X docs).

After getting burned by the dumpster fire that is Amazon Honeycode, I wouldn't touch this with a 10 foot pole.

yanlezeiler 5y ago

What's wrong with Honeycode ?

istjohn 5y ago
1. There is no data export tool. The only way to pull data out is either to copy and paste from each and every table into Excel or Google Sheets and export from there to CSV or to roll your own custom export script using their poorly documented JS API. 2. Once you have more than 3,000 or so rows in a workbook, everything grinds to a crawl. It can literally take over a minute for any kind of data mutation in the administration user interface or in the app interface to be reflected in the display. This means that doing anything on the app becomes literally slower than if you were to do it with paper and pencil. And this is despite paying $20/month for the Plus tier, which purportedly allows 10,000 rows per workbook. 3. The project lacks polish and user-friendliness throughout. 4. It is buggy throughout, and developer updates have introduced new bugs multiple times. For example, recently the last record in a table started getting displayed in my app view even though it is excluded by the list filter in that view. 5. The bug reporting process is difficult to the point that I don't even bother anymore. 6. The first time you try to open an old workbook, it will error out. Presumably they are using serverless and the Lambda function is cold.

amzn-throw 5y ago

Amazon/AWS teams are so distributed and independent that it the quality of the output of one team very rarely reflects in any way on the quality of the output of another. This is almost always a good thing. There are of course centralizations and standardizations - the AWS SDK, Console UX, API guarantees, etc. But Honeycode has almost no relationship to the rest of AWS, technically, or organizationally.

IceDane 5y ago
Except what this really means is that nearly any part of AWS you have to deal with has been clobbered together by a series of different teams with little cohesion. The last time I dealt with AWS and amplify, this was glaringly obvious in several places. Settings pages where one tab looked and behaved radically different from the other. A seeming total lack of communication between teams resulting in badly synced package released with bugs due to version differences. Also frequent omissions in documentation requiring you to hunt it down in github repos or in totally different places(Say Amplify uses X to do something, you might have to find info for using X in an Amplify context in the X docs).