I do not specialize in mobile development.

In truth, if not for frameworks like Bootstrap, I would be content to pretend mobile browsers did not exist at all.

This last week, while writing my own basic font editor for the `Articles` section of Resalient, I was playing with some fun fonts such as `Old English Text MT` and `Stencil`; and when double checking it on my phone, I found out that generally speaking only "Serif" and "Sans Serif" (and "Cursive") exist on my phone. (For anyone curious, I tested in Brave, Chrome and Edge Mobile on a phone still receiving support and updates.)

If you have ever played with "Touch" vs "Click" events between mobile and desktop, many of these differences will not surprise you. In another article, Manage Activities by Touch, I reference the use of a 3rd party library to enable Touch for Task management. A similar work around could be used to embed fonts that are downloaded specific to the website...I do not have a good justification, but I will not be doing this.

Where does that leave Resalient?

A few years ago, several text editors moved to a ribbon styling system and away from the classic fine tuned controls (only to later revert or implement each.) At the moment, for the sake of mobile, I am going to shift my focus to a ribbon with specific styling.

Could Resalient use a 3rd party control for text editing?

Perhaps.

One that caught my eye was TinyMCE (with both a free and paid version.) While the features were amazing, I could not imagine end users of Resalient using the full capabilities of TinyMCE.

At the end of the day, `$(_element_).toggleClass(_example_class_)` for each possible style is not that hard to code; and with that in mind, rolling a custom control will allow Resalient to better tailor the experience to the end user.

Keep in mind, do not let perfection be the enemy of completion. There will always be a better widget. The things you learn next year will change the assumptions that drove last year's practice. Never stop adapting and evolving your systems.