Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Modernization #46

Open
nearwood opened this issue Nov 7, 2019 · 0 comments
Open

Modernization #46

nearwood opened this issue Nov 7, 2019 · 0 comments

Comments

@nearwood
Copy link
Owner

nearwood commented Nov 7, 2019

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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant