Yes, indeed google quite some time ago has blocked the possibility to login to it's services via app's internal WebView
. The reason is that Google does not trust external app providers, where it is't aware of security of connection. It forces external app providers to use Google's methods of login to it's services.
Source: Modernizing OAuth interactions in Native Apps for Better Usability and Security
Indeed you have found the right methods to use Google services, however, Firebase and Google Sign In have disadvantage that makes them unusable by you, namely both need Google Play Services. Firebase needs them and Google Sign-in needs them. So there is no official way of using both on devices not having Google Play Services.
There is yet another way: Chrome Custom Tabs. However, they require Chrome installed on the device. And since a long time it also uses Google Play Services. Moreover, Chrome Custom Tabs have been introduced later than Chrome has incorporated Google Play Services
However, there's a hack. Declare app's internal WebView's User Agent as Chrome. Here is the documentation. As seen at the bottom of this page, you could remove following Strings from WebView
User Agent String:
Version/_X.X_
on Kitkat Devices
wv
on Lollipop+ devices.
However, I do not recommend this method and kindly encourage to stick to Google Policy, if there is a possibility.
Hope that this explanation is enough.
EDIT:
As per comment below, Goole Api Java Client does not need Google Play Services, so this might be an option.