Sooo after returning from my 3 weeks of vacation (student part-timer so no real obligations) I learned that the last two months of work refactoring our legacy app to conform to modern Android app standards, is being shut down because we begin to rewrite everything for cross platform...
Not sure how I feel about it, because I really liked Android development and I poured my heart in it... On the bright side: I'll get to learn more Javascript, HTML, css and polymer stuff which I guess is good.

It still stings a little 😥

oh hey another company whose apps i wont use

May I ask why? I mean we simply don't have the manpower to maintain native Android and IPhone apps, so cross platform was the only choice to deliver to the different user bases we have.

Ours is a real app which requires app like features we can't simply do a Web interface (but want to maybe have such a version too If possible with polymer).
I don't exactly know the breaking point for that decision, but in our case we need offline capabilites and dynamic rendering stuff. I can't get into more details sadly but from my perspective it's the offline stuff which is our breaking point. If we'd have a Web interface it simply wouldn't do the job. I think...

js apps run a lot slower and cant access native hardware fast enough and i hate sluggish apps

also if you can make it as a js app, you can make it as a website

xamarin seems to be an exception, but i dont have enough experience yet

As I understand it the polymer app toolbox allows development for a fast progressive webapp with offline functionality. Maybe it isn't as fast as native apps but in my understanding ithe difference should be negligible.
I'm not sure how my superior wants to implement cross platform opengl rendering and PDF viewing, but I think they thought this step through for quite some time, so they should have found a way.
Since I'm just starting to get into polymer that stuff is too advanced for me, so I won't look for it now.

Also I don't really know what you mean with "sluggish" app? Just because it's JS it doesn't have to be sluggish... Or does it?
Maybe it's easier to drift in bad practice programming but I think it's possible to maintain a high quality with enough planning and care.