react-native-intl-phone-field VS libphonenumber

I created a library that simplifies the validation and formatting process of international phone numbers: react-native-intl-phone-field. It's built using Google's library libphonenumber and phonenumber-js & it's not much by it's honest work.

libphonenumber can format in many ways, you can find the national patterns in the metadata files https://github.com/google/libphonenumber/blob/master/resources/PhoneNumberMetadata.xml

For instance, the XML file https://github.com/google/libphonenumber/blob/master/resources/PhoneNumberMetadata.xml contains Phone number metadata with possible lengths, broken down by countries.

From falsehoods developers believe about phone numbers :

This makes the assumption that Twitter blocked it due to SMS fraud. While that's a plausible theory an equally plausible theory is that they were worried about account hijacking and security (and allowed twitter blue subscribers to continue to use it on a you can pay me to be stupid context) which seems equally plausible.

I take issue with a lot of the assumptions in the article but this is funny:

> Identify and block premium rate phone numbers, using libphonenumber. Whilst this seems promising, I don’t know how reliable the data and how effective this approach is.

here's this purpose-built and well maintained* library from google which does exactly what I want but i'm not even going to consider it.

* the actual number database has been updated 5x so far this year: https://github.com/google/libphonenumber/commits/master/meta...

Yeah, but you can probably use https://github.com/google/libphonenumber for that.

You can find the Github repo and documentation for the library here.