@josesaezmerino its for clarity. when you have a ton of tabs opened is quite hard to manage and see their names. this makes sense and gives an alternative view, which is nice as we shouldn't force just our way into products.
@joni_vrbt If you shipped it and it works, you built it. The path doesn't matter. Vibe coding with experience behind it produces real results. The gatekeeping around "proper" process is mostly theater anyway.
@disco_lu Spot on, but I'd flip it. Primary isn't a token name, it's a placeholder. Real names are primary-action, primary-text, or whatever. Specific naming reduces friction and speeds adoption far more than documentation could. Documentation masks bad naming short-term, but doesn't scale
@disco_lu Spot on, but I'd flip it. Primary isn't a token name, it's a placeholder. Real names are primary-action, primary-text, or whatever. Specific naming reduces friction and speeds adoption far more than documentation could. Documentation masks bad naming short-term, but doesn't scale
@disco_lu Agreed. But the current trend is actually forcing people to do the jump. Designers are being pressured. we shouldn't be afraid of calling what it is.
@moonymarss Because you don't need an iPhone. It works even better on android since updates are not tight to os updates. Some features/fixes even get released first on android.