Looking for a little bit of advice / pointing in the right direction. Our Sales Admin team is burned out getting blamed for bad address input. This it was possible to add a field where they can type in an address and it calls, USPS, Google Maps, and Bing Maps to get a 3 way match. So I signed up for a dev account and have that working. On field change, call out to those services and it returns the values in a field with a little checkmark. Here is where I need advice...They hate the user experience The UI freezes for a few seconds, Sometimes they tab out of the field too soon, overwriting is a pain if they mess up, etc. What they are asking for is it to not happen on field change, and more like a special field with a search button next to it to submit, and a loader / progress bar on the search and return a list. Any suggestions for UI / UX pattern? FYI - this IS NOT on bill to / ship to address stuff on Customer or Transaction. It's the address we added to Work Orders.

I'd just launch a suitelet and let them go nuts. Then they can select the one you want and you can use window.opener(...) to get a handle to the calling window and call back and set the value. Its quite a bit of work but it'll decouple it. IMO You don't want to get into loaders and progress bars in netsuite as you gotta use non-standard/supported (in regards to netsuite) development practices.

Look into debouncing and asynchronous requests (e.g. https.get.promise) to improve UX. When I worked on something similar, I added a custom field for an address typeahead, disabled the native fields, and then it when a valid address was selected it automatically populated the native fields.

Thanks to you both! @michoel any recommended reading on these. I have read through the promise object in SuiteAnswers and think I understand but was looking for some more examples. If you dont know of any, no worries.