Excessive metadata instantiation for PhoneNumber.parse().isValid(), 245+ object instances created unnecessarily

[YazanFarrah]

When calling PhoneNumber.parse('+$phoneNumber').isValid(), the package initializes hundreds of PhoneMetadata-related objects in memory on each import, regardless of the country used.

After profiling, these are the counts observed:

PhoneMetadata → 245 instances

PhoneMetadataPatterns → 245 instances

IsoCode → 245 instances

PhoneMetadataLengths → 178 instances

This initialization occurs even when validating a single phone number, resulting in unnecessary memory usage and slower startup.

Expected Behavior:

The library should lazily load or cache only the metadata required for:

The detected country code, or

The specific ISO region used during parsing.

This would reduce startup overhead dramatically.

[cedvdb]

Metadata maps seems to be const so they may be instantiated once at the start but you seem to say those are instantiated again after PhoneNumber.parse('+$phoneNumber').isValid() ?

Initializing all metadata initially is necessary when you don't know the iso code in advance.

I'm sure there are optimizations that are possible, so I'll gladly review a PR, but it may be useful to describe here what process you'd have in mind to optimize this before hand.

Another option would be generating patterns on demand instead of having a global const map

PhoneMetadataPatterns getPattern(IsoCode code) {
  switch(code) {
    case IsoCode.AC:
      return PhoneMetadataPatterns(...);
    case IsoCode.AD:
      return PhoneMetadataPatterns(...);
    // more cases
  }
}

[iosephmagno]

#105

[iosephmagno]

@cedvdb thanks for this plugin! We are using it in Presence Messenger.