Reply To: Maseter Port Out PIN

[Andrey]

#13874

Hello Nishit thank you for these details, so from your reply above #13872
firstly: – I understood that we have done an API code and API instructions for our API users which we all API library and this work well from our side. The only problem is that we no loner need API calls for brands but these are in our API library – which probably confusing our customers.

secondly – Since we have done Matching Numbers job and that may have more same numbers appearing in the different areas also affecting our API library encoded version.
These above bringing us to a stage when customers would like to fetch more numbers from our DB and this causes our site resources handling with it and as a result we experiencing slow browsing issues.

If I got it right we may need to modernize our API library and adopt it functionality to the above mentioned realities.

As a result please Nishit continue on finishing this Job including bug fixes reported earlier,: – the site browsing speed is now better I can confirm that. Reserve number button still to be fixed so please fix this as well then we may need to do a Junk Param job ( being planned currently) which will bring us closer to the API Improvement Job.

While on these tasks we will be working on API Improvement job road map and when we come to that we also ask your opinion on how to make this work professionally effective and maximum transparent and manageable for the EN site administration.

Please also make your resolution thoughts on the #13870 how we can standardize the project layout.
Kind regards Andrey 🙂