It enables Gleam developers to write Gleam code in a wider variety of situations. Web frontends are one obvious example (though as you say there are more mature

It enables Gleam developers to write Gleam code in a wider variety of situations. Web frontends are one obvious example (though as you say there are more mature ecosystems for that) but there are many others, some of which are listed in the post. I think it is unlikely many people will pick Gleam to make just a web frontend, but if you have a Gleam backend it may be more appealling to also use it on the frontend so that you can share code and type definitions between them. In future a full stack Gleam web framework may also take care of the typically JSON API boilerplate between the front and back ends. I can see myself using Gleam on AWS lambda and on Android in the near future using the JavaScript backend.