Love the front-end builder, but my use case for this and I believe for many others is if we can either route ALL backend calls through lambdas (including CRUDL and Cognito/Auth) or at the least if we can route all data persistence to DynamoDB tables within our own accounts that we can trigger off of.
Any more complicated user stories like syncing data to DDB would be helpful as well or supporting triggers on all UI events via Lambdas or RESTful APIs would also work. But ideally, whatever data is persisted from Honeycode should be visible in our own AWS accounts.
The most basic use case is this:
Company spends $X developing mobile or web apps, but backend admin and supporting apps are down-prioritized as not part of MVP, but they are essential. To have honeycode support our existing S3, DDB/DAX, or RDS and lambdas on the backend allow all of these LOB apps to be built UPON existing app infrastructure (instead of all-new infra as it appears to do now).
By limiting the backend to all-new non-accessible backend storage, honeycode becomes ONLY useful in dead-ended apps which IMHO is not that useful.
Cheers,
Rob