Final note from me:
There is more stuff broken and fallen into the gutter beside the path NC chose.
I think more apps are broken in the app store than working.
I have no definitive idea about how to prevent this from reoccurring.
One idea: Ensure the Documentation (valid for the API) is published AHEAD of beta releases so developers can adjust.
(That also would imply there is some actual engineering going into NC).
Currently the practice seems to be throwing some Beta release over the wall, see what fallout it creates, fix that then describe remaining stuff into docs …
And hope the previous creators of APPS do follow…
(The release notes part, the API docs is a hotch potch of NC15 examples, NC17 Code, intersperced with NC11 descriptions… etc. trailing the current release with at least about a year worth of updates).
I just now wonder how long VUE will be used, 1, 2 or 3 versions before it gets replaced with the next whimp.
I’ll continue to use what works for now. and let go of some functionality if the next app falls down the side. Now it is pico_cms, before : pdfreader, files_opds etc.
I do develop code, just No web apps, no PHP, no Vue etc. I tried 2 years ago to revive some App only to find the state of mess called the NC X API which only loosely correlates to NC X+1 or X-1 API’s, less so to X-2 or X+2 API’s.
Learning everything is beyond my available time, and obsolete before i get enough grips on it.
On closing note: Maybe it would help to have NC developers assist App developers 1:1, it might also help the NC developers see HOW people actually use the platform…