Markdown files are an easy way of structuring some quick notes.
Although their plain textural representation is already well structured, adapted rendering for phones would allow these files to be even more useful.
That way one could take down notes on the computer, sync them with Nextcloud to the phone and have an easy to read representation on the phone.
The android app is currently displaying text files within the app. It would be nice if it could render Markdown files in preview mode, i.e. similar to HTML.
There are apps on the Android app store that allow editing and preview of Markdown files, however using them for preview is rather cumbersome compared to previewing Markdown files within the Nextcloud Android app.
GitMate.io thinks possibly related issues are https://github.com/nextcloud/android/issues/810 (Preview Media Issue ), https://github.com/nextcloud/android/issues/503 (Preview of downloaded files not working), https://github.com/nextcloud/android/issues/1854 (.mp4 preview missing), https://github.com/nextcloud/android/issues/2006 (Sorting order on preview not correct if file list is != a-z), and https://github.com/nextcloud/android/pull/3216 (Add has-preview property).
@tobiasKaminsky I am fine with the assessement that this is a feature while I'd like to disuss it and it's implications so I'd also like to get @stefan-niedermann's input on adding "just the rendering".
So to be discussed (from my point of view) and rendering would be fine with me (scope of this feature request) while editing capabilities is something I'd rather not add to the files client. (same arguments would also apply for deck, bookmarks, you name it)
Related: https://github.com/stefan-niedermann/nextcloud-notes/issues/439
I think it would be a better home in the Notes app - Download the file with the files app and open it with the notes app might solve the issue.
Though "just rendering" is quiet easy - basically at a dependency and use a subclass of TextView.
But beware of further feature requests if you implement it in the files app, you will get a new issue for every missing or buggy feature in the lib (like suport for tables, checkboxes and so on)
There's no smoke without fire
I think write support would still be different. Notes are notes and can live in the notes app, which provides more specialized features for that task. But if there is much demand for simple read/write support in the client – why not?
But that demand hasn't been claimed yet. I'd also love to see the markdown rendering feature in the android app.
Also, there is no right to deliver all feature requests. So personally I wouldn't care too much about this virtual threat.
Another point for possible subsequent feature requests for write support: There isn't even write support for simple plain text files. So then write support for markdown files is much further away.
PR adding initial support is #4692