You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Application is ancient by modern web standards. Works fine, but the combination of PHP + jQuery + custom CSS doesn't lend itself to mobile development very well. ~80% of traffic is from mobile.
Having a usable mobile interface would help people using a laptop (possibly without internet) to tune, but want to compare on a mobile.
Ideally, the data would be completely separate from the view (eg, split into API and front end).
Options:
Rewrite/migrate to Laravel
Pros: Has built in ORM, testing, frontend scaffolding and other nice features
Cons: Possibly overkill, but actively maintained.
Rewrite as API (with Laravel, Express/Koa)
Pros: Completely separates data from view. Allows other apps to access it (msdroid guy)
Cons: Have to come up with comprehensive API that handles all MSQ weirdness, and front-end
Rewrite as client-side app
Pros: Could be PWA, work offline (useful when on the road), fast React development
Cons: Have to rewrite everything in JS. Locked in to React/Redux.
The text was updated successfully, but these errors were encountered:
Application is ancient by modern web standards. Works fine, but the combination of PHP + jQuery + custom CSS doesn't lend itself to mobile development very well. ~80% of traffic is from mobile.
Having a usable mobile interface would help people using a laptop (possibly without internet) to tune, but want to compare on a mobile.
Ideally, the data would be completely separate from the view (eg, split into API and front end).
Options:
The text was updated successfully, but these errors were encountered: