ex_phone_number
An Elixir library for parsing, formatting, and validating international phone numbers, based on Google's libphonenumber.
What is ex_phone_number?
ExPhoneNumber is an Elixir library for parsing, formatting, and validating international phone numbers. It is a direct port of Google's libphonenumber, providing reliable tools to handle phone number data according to global standards. The library solves the problem of inconsistent phone number formats and validation across different regions.
Elixir developers building applications that require phone number input, validation, or formatting, such as user authentication systems, contact management tools, or telecommunication services.
Developers choose ExPhoneNumber because it brings the battle-tested accuracy of Google's libphonenumber to Elixir, with features like custom metadata support and LLM integration guidance, ensuring robust and maintainable phone number handling.
Overview
Elixir port of libphonenumber
Use Cases
Best For
- Validating user-provided phone numbers in Elixir web applications
- Formatting phone numbers for display in international user interfaces
- Parsing phone numbers from various input formats into a standardized structure
- Ensuring phone number data consistency in Elixir-based databases
- Integrating phone number handling in telecommunication or messaging services
- Building authentication systems that use phone numbers as identifiers
Not Ideal For
- Projects built in programming languages other than Elixir or Erlang
- Applications requiring real-time phone number carrier detection or geolocation services
- Systems with strict memory constraints where the bundled metadata size is prohibitive
- Use cases limited to single-country phone validation without international expansion plans
Pros & Cons
Pros
Direct port of Google's industry-standard library, ensuring accuracy and reliability for parsing, validation, and formatting of international phone numbers.
Supports multiple standards like E.164, international, national, and RFC3966, as shown in the usage examples with clear output formats.
Identifies phone number types such as fixed-line or mobile, useful for application logic based on number characteristics.
Includes usage rules for AI assistants to prevent common mistakes, aiding in correct implementation and reducing integration errors.
Cons
Setting up custom metadata requires recompiling the dependency with absolute paths, which is cumbersome and adds deployment overhead.
As a port, it may not immediately reflect the latest libphonenumber updates; the README notes current metadata version, but updates depend on maintainer activity.
Exclusive to Elixir, making it unsuitable for polyglot projects or those not using Elixir, limiting its versatility.
Frequently Asked Questions
Related Projects
AtomVMTiny Erlang VM
porcelainWork with external processes like a boss
hammerAn Elixir rate-limiter with pluggable backends
cubdbElixir embedded key/value database
Found a gem we're missing?
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.