Dead project?

[James-Parsons]

It seems that many examples / frameworks are outdated or missing and there have not been many commits recently. Is this no longer maintained?

[ColinEberhardt]

Thanks for your interest @James-Parsons - that's a very good question.

When we first started this project in 2012 we felt there was a very real need for it. The HTML5 vs. Native debate was very 'hot', however, the arguments for each side seemed to be based on opinion and hyperbole rather than facts, For that reason we decided that a 'ToDoMVC' for mobile would be a really great way to allow people to objectively compare the various options.

However, things have changed quite a bit in the past 5 years. Interestingly the HTML5 vs. Native debate was never really resolved, and there are some decent options available on both 'sides'. However, with progressive web apps, there is a very real alternative for creating mobile apps outside of the app store (which is what PropertyCross focusses on).

Current this project has a number of issues:

• Maintaining the various PropertyCross implementations is a massive task, what started as ~ 5 different frameworks is now 26, each of which can vary between the different mobile OS, giving a significant maintainance overhead
• Nestoria has changed their API, which has caused some of the app functionality to break Most examples are broken due to API change #337
• There are some highly significant frameworks, such as ReactNative that are not featured on PropertyCross.
• We have some 'old' frameworks such as jQTouch and jQuery Mobile that I feel should be removed
• Many of the PropertyCross examples are probably quite dated and require framework updates.
• While the PropertyCross app is relatively simple, it still requires quite a bit of code in order to be implemented. This makes it quite hard to ensure quality
• We don't show how PWAs compare.

I don't think any of the project maintainers have the time (or desire) to keep this project going. Unless someone else volunteers to become a maintainer I propose that the website and GitHub readme are updated to have a prominent link to this comment (or a version of it) so that people are made aware of the current project status and are no misled.

@tastejs/todomvc

[sindresorhus]

👍 to updating the website with maintenance status.