Hey, I agree with Pankaj Patel Ionic seems to be a good choice. the idea of Argjend about using electron probabily in combination with phonegap or something similar is also a valid option
changing from angular to a React by utilizing react native where rendering part is done native but the business logic is written in JS is also an option although we would add a bloat factor to your techstack
I would consider the following things:
if one of those two points is a match you probably should go with a hybrid app so you don't have multiple code bases and you can in theory code efficient JS.
if this is not the case but the app looks different and it does not change that often we could consider a native app since the overhead of maintaining it etc is not an impediment.
the next things we need to consider are values and constraints. what are our values? what are our constraint? what are our goals?
Those are things you have to consider by picking a stack. Maybe you want to build up competence in a certain technology because you want to move towards it or it's highly beneficial to your company in the future.
if you are not sure at all and this is way beyond the problems you want to consider the answer is pretty straight forward.
Ionic. least overhead, dynamic updates, you already know the framework it's based on.
otherwise think about what you want to achieve and how you benefit from it before starting a new learning curve, frustration level and velocity loss with technology/stack hops.
I hope this makes sense :)