Basic Angular (2 or 4) knowledge might be missing here, but this course will definitely allow you to solve this multi-language issue.
You might need to pick up some basic Angular 2 course to dive deeply into this course but once you did this, you definitely should join!
Input validation should happen as early as possible in the data flow, preferably as soon as the data is received from the external party.
Data from all potentially untrusted sources should be subject to input validation, including not only Internet-facing web clients but also backend feeds over extranets, from suppliers, partners, vendors or regulators, each of which may be compromised on their own and start sending malformed data.
Ionic 2 will handle the rest and compile your code for you.
This allows you to focus on the things you know and release your application on all possible devices (desktop and mobile) without having to learn thousands of different languages!
Input Validation should not be used as the primary method of preventing XSS, SQL Injection and other attacks which are covered in respective cheat sheets but can significantly contribute to reducing their impact if implemented properly.
You should dive into Angular first so that you get a feeling for how it works and which problem it actually solves.
Angular 4 is the future of Angular, the same is true for Ionic 2!
Student #4 Has basic HTML and JS knowledge and would love to develop native apps with that knowledge!
Or join now and just learn Angular 2 along the way! Ionic 2 uses Angular, which is a complete re-write of Angular 1.
Student #3 Already knows Angular 1 and Ionic 1 as well as some basic Angular. Therefore, Ionic 2 also distinctively differs from Ionic 1 and really embraces the component-driven approach of Angular.