> "To us, Prosemirror stood out as the most powerful solution. We wouldn't have needed any third-party dependencies (except for a React integration) and would have been able to define our document schema from the ground up. We didn't go with it because it took a lot of code to get started (even the official ProseMirror guides state this) and defining our custom schema, while powerful, was not worth the effort since we didn't have many custom requirements."
Custom schema is not just powerful but also essential for cross platform rich text editing/rendering. For example most rich text editors that work really well on the web is almost always broken in some way in a native android/ios app. Why? usually we ignore the schema and dump a black box json/html as rendering format and then deal with editing issues with that format when we actually port the app to mobile platforms.
For me it makes sense to just go with markdown or a very customizable rich text schema if it's worth it - so that rich text editing works smoothly across platforms.
Custom schema is not just powerful but also essential for cross platform rich text editing/rendering. For example most rich text editors that work really well on the web is almost always broken in some way in a native android/ios app. Why? usually we ignore the schema and dump a black box json/html as rendering format and then deal with editing issues with that format when we actually port the app to mobile platforms.
For me it makes sense to just go with markdown or a very customizable rich text schema if it's worth it - so that rich text editing works smoothly across platforms.