Tina is designed to give editors the live editing experience they want (similar to a site builder like squarespace) while developers maintain control over the project. NetlifyCMS is missing the former. They have their preview templates but it is not an exact representation and requires extra work from the developer.

Tina is also designed so that you can create the editing experience that your customers/clients/coworkers need. Instead of a one-size-fits-all solution, you can give them something that is tailored to their needs.

As well, at the moment Tina only works with git (similar to NetlifyCMS) but we are working on other data source plugins as well (think Contentful, Headless Wordpress, etc).

The 'requires extra work from the developer' would be the main way to improve on NetlifyCMS. You have to create a schema, and then translate the schema and any changes into an editor component. How does Tina do it without this?

I'd do a quick demo for your client/team and see if they have a preference.

Wondering this as well!