@bholagabbar, it’s up to you and @maimoonak to decide on the best way to use the GSoC time to work on this project, and we will support whatever decision you make.
I disagree with two things here:
- OWA does not require any specific JS library, and it definitely doesn’t require Polymer. Although I would personally recommend that you take advantage of this opportunity to learn how to use a modern JS tech stack (e.g. following what @raff and soldevelo interns are working on here), you could also do an OWA using jQuery and bootstrap.
- I understood from the design call that there is not very much existing UI, and you’ll be adding a lot of new screens and features, relative to what’s there now. From glancing at your mockups, I would think that writing from scratch in any technology other than JSP is going to be faster, even accounting for the learning curve.
Is this different from what I suggested on the design call, which is to rewrite the UI while adding your new features? (Maybe we’re just using different terms for the same thing, but I don’t know how you would “revamp” a JSP-based UI to use jQuery and Bootstrap in a way that’s different from a “rewrite.”)
Regardless, if I’m understanding you right that this will be HTML + JS client-side code, you should do this in an OWA.
I’m assuming that when you say you’ll use jQuery and Bootstrap that you intend to make this more of a client-side app. If that’s the case, REST endpoints need to be redone as part of Phase 1. (But I thought the REST endpoints were already nicely functional.)