I am looking for a way to implement a "shopping cart" like functionality while balancing "user experience" and software quality.
In my case I have a classroom with students and need to handle the following list of functionalities:
- add/remove students to/from class
- manage students' scores
I was told to implement modal with AJAX, but I would rather keep use of JS to minimum and implement things on the server. I came up with two simplified mock-ups and analyzed pros and cons.
Mock-up with AJAX:
Mock-up without AJAX:
Pros and cons of each
- "Modern" look and feel
- End user may like the fact that they can complete all the work from one page, without having to jump from page to page
- Too many functionalities on one page (update scores, filter table, arr/remove students)
- Too much JS (I would rather write code in object oriented language with strong typing)
- Single page - single responsibility
- No JS (all code is in one place, better debugging, easier to read code and to maintain, etc)
- I would have to pre-load ~10000+ records into the table, which can be time consuming
- Not so "responsive"; have to jump from page to page rather then finish doing everything on a single page
- What would be "the industry standard" to go about it?
- How to go about taking advantage of both?
I felt the need to specify that this is somewhat "internal" application. It is not going to be open to "general public". There will be maybe under a ~100 (or a few hundred) people who will use this application. In addition, there probably will be just 2 people at most working on this application. We don't have resources Facebook or Google has to build heavy one page web apps. We are not even allowed to use frameworks like angular. I would use jQuery's AJAX.