I've written an article about Frontend Platform Engineering that I would like to share here. I'd like to connect with people working in this field. I will be in London for the PlatformCon Live Day for that entire week. If you want to connect, please send me a DM! https://www.frontenderz.io/blog/frontend-platform-engineering.-what-is-it-and-why-do-i-need-it

BFF are just as population for this, yeah?

I'm sorry, what do you mean?

This is awesome and perfect timing. I’m starting a new position as a FE engineer on a Platform team. I have always been a product developer so it’s great to learn more about what FE platform engineers do

BFF - Backend for Frontend

I know what BFF means, I just don't understand your sentence/question

Nice one Jouke!

Sorry, I see my typo should have said popular. My point was that , yes, frontends are good for looking at, but backends truly drive the interaction. So, you're a full stack developer more often than not. Alternatively, with the proper backend design, your frontend could be Terraform, k8s operators, or CICD triggers rather than another UI portal within an org

I'm not going to argue with you here, let me just say I think you're misunderstanding me. If you're only looking at making an appropriate screen for a backend service (BFF or not), then your approach to Frontend Development is different. I'm talking about a full-fledged Frontend Application with many teams working on many features. Questions pop up like how do you keep up with dependencies in terms of regular Lifecycle Management as well as security patches. How do you integrate all these features? How do you make sure not everyone is reinventing wheels? How do you offer Golden Paths for Frontend Developers?

And my argument is that those same problems exist on both sides of development. My experience with frontend has always been different teams own different components then there's a broader release cycle for the client facing "main application"

Then we agree 🙂 . The thing is, hardly anyone speaks/writes on how to properly do these things at scale for Frontend Development, and many organizations just don't have their Frontend Plaform at thr same level as their backend Platform.

I find Backstage makes this quite easy, though some find the built-in Material UI based components to be limiting (at least having seen Adobe toss in their whole Spectrum UI components as a brand new frontend interface)

Just so we're clear: implementing Backstage is NOT the same as having a Frontend Platform. Backstage is a Frontend for your Internal Development Platform. A Frontend Platform supports your Frontend Developers build client-facing Digital Experiences.

That just sounds like a component library / Storybook, with iconography + UX flows/animations, not "a platform"

Maybe this article I wrote recently clears up what I call a Frontend Platform https://www.frontenderz.io/blog/frontend-platform-engineering.-what-is-it-and-why-do-i-need-it

Over half of this seems like what every other company is calling infrastructure and backend DevOps