A word of warning: if you ever set out to handle international numbers in a web frontend - you may think "it can't be that hard - maybe take me a couple of hours" (like me), then do yourself a favour and save yourself a week of unexpected work and use the jQuery plugin that I ended up creating (I don't understand why this didn't already exist) which uses libphonenumber for all the magic: https://github.com/Bluefieldscom/intl-tel-input. Hope it saves you some time.
Google's phone number handling library
11–20 of 44 posts
Re: Google's phone number handling library
#12I use the PHP version from time to time. https://github.com/giggsey/libphonenumber-for-php
Re: Google's phone number handling library
#13As someone who does a lot of telephony work, <333
Re: Google's phone number handling library
#14Not entirely sure how this made front page, but it is a super handy lib. I don't understand why Android includes this lib in their source but makes it internal so you have to provide your own copy if you want to use it in your app: https://android.googlesource.com/platform/external/libphonen...
>> Not entirely sure how this made front page, but it is a super handy lib. Sad that nowadays a statement like that isn't even considered ironic :). A cross-platform library handling an ugly necessity of development has to fight for its life in a sea of "growth hacking 101" links and the like.
Re: Google's phone number handling library
#15Not entirely sure how this made front page, but it is a super handy lib. I don't understand why Android includes this lib in their source but makes it internal so you have to provide your own copy if you want to use it in your app: https://android.googlesource.com/platform/external/libphonen...
The reason it's internal is because system code takes priority over third party libraries given the same package name. If there were any changes to the library, you could never use the newest version because it would be dominated by the system version. This is what happened to the Apache HttpClient and why there is a fully repackaged version[1] for people who want to use a newer client than the one in the Android Sys…
Re: Google's phone number handling library
#16Why, for example, is Stripe leading the charge on decent credit card front ends when Visa could spend a few million and produce the one and only Unicode, works everywhere, looks up addresses credit card entry form.
Why is an advertising company doing this when any of the major telcos have this internal knowledge lying around?
The blindness does seem almost wilful at times.
Re: Google's phone number handling library
#17Not entirely sure how this made front page, but it is a super handy lib. I don't understand why Android includes this lib in their source but makes it internal so you have to provide your own copy if you want to use it in your app: https://android.googlesource.com/platform/external/libphonen...
>> Not entirely sure how this made front page, but it is a super handy lib. Sad that nowadays a statement like that isn't even considered ironic :). A cross-platform library handling an ugly necessity of development has to fight for its life in a sea of "growth hacking 101" links and the like.
Re: Google's phone number handling library
#18I've been using this for quite a while -- it's excellent -- without a doubt the best library around for dealing with phone numbers in E.164 format (the international standard). As someone who does a lot of telephony work, <333
Re: Google's phone number handling library
#19Re: Google's phone number handling library
#20Really nice.