[HN Gopher] AWS Amplify Studio: Figma design to full-stack apps
___________________________________________________________________
AWS Amplify Studio: Figma design to full-stack apps
Author : revskill
Score : 58 points
Date : 2021-12-03 08:32 UTC (14 hours ago)
(HTM) web link (aws.amazon.com)
(TXT) w3m dump (aws.amazon.com)
| node-bayarea wrote:
| Remember, many of these things that get released are usually just
| vaporware. They may become better 6 months or a year later, or,
| they may never see the light of day.
| arpinum wrote:
| Amplify constantly under delivers. Features are built only enough
| to make a demo. Now they say they can go from design tool to
| working app, where dozens of companies have failed over the last
| 25 years. Call me skeptical.
| simse wrote:
| At what point is AWS too big? Or should I say, when did they
| become too big?
| istjohn wrote:
| After getting burned by the dumpster fire that is Amazon
| Honeycode, I wouldn't touch this with a 10 foot pole.
| yanlezeiler wrote:
| What's wrong with Honeycode ?
| eunoia wrote:
| I was working heavily with amplify a couple years ago and to be
| honest it was an awful experience.
|
| Common use cases weren't handled well, deployment failures were
| common, overall architecture was actually less coherent when
| using amplify than just the constituent AWS services directly,
| etc...
|
| It felt like a kitchen sink of functionality that no one was
| incentivized to actually make work well together.
|
| Have things improved?
| sbashyal wrote:
| Not a whole lot based on our experience few months ago.
| loh wrote:
| May I ask about your (and eunoia's) use case(s)?
|
| Coincidentally, 2 hours ago I submitted Molecule.dev right
| here to HN (an hour before this AWS submission), a full-stack
| solution which aims to address all of the time consuming pain
| points of building (common functionality), maintaining, and
| releasing cross-platform apps.
|
| It isn't a UI builder like AWS Amplify Studio, but I think we
| can do it better. We cover all of the most common use cases
| and are planning on adding more, all without any vendor lock-
| in or unnecessary convoluted abstractions.
| tluyben2 wrote:
| That looks interesting; will give it a go in the weekend.
| sjg1729 wrote:
| Nope. I made the mistake of architecting my current project
| around Amplify. Deployment errors are thankfully rare these
| days, but things that should be easy are hard, and there are
| many seemingly obvious use cases that the Amplify CLI doesn't
| handle.
| nicoburns wrote:
| I would like Figma themselves to have a go at something like
| this. Their auto-layout system is close enough to being flexbox
| that you can actually make decent responsive layout with it. I
| think a way to export that could be quite useful if done well.
| Especially for prototypes.
___________________________________________________________________
(page generated 2021-12-03 23:00 UTC)