They're more concerned with rolling out their premium tier than with protecting their users' nsecs. Allowing sign-in with Amber should have been enabled long before v2.0.
Discussion
Youβre comparing their speed of implementation to android specific clients, keep in mind theyβre working simultaneously on web, iOS & android.
they also released android like 4 months ago compared to the ones youβre thinking of that have been around for longer than a year and have a shit ton of contributors lol
give it a years time, and everything will be left in the dust. 
I get what you're saying. It's really a matter of priorities. And while I believe I may have prioritized things differently, I'm not privy to their thought process, and their reasoning for choosing to prioritize certain things over others. It's just frustrating to me because I see external signer support as a fundamental feature that every client should support on day one.
Unfortunately Iβm on IOS so I havenβt experienced external signer support from any IOS client, Iβve had to raw dog my nsec into every single one of them..
i agree that it should be at the top of the list idk why it isnβt, if itβs because itβs harder to implement then i understand but if itβs bc itβs not a popular request then I donβt..