It seems like a shipping-address form would be make a good standalone web component. I don't suppose one already exists?
6
Replies
·
0
Boosts
I suppose the problem is that it's either just-a-form (no web component necessary) or it has to access an address validation API – and then it's not really stand-alone. So maybe never mind.
@mia When using address validation it depends a lot how you present that to the user. Ideally you want the user to type as few fields as possible, providing only valid suggestion when filling in fields. Which fields are required, which optional, and in which order, depends on the country and the validation API. Some providers offer their own frontend components if you want to follow their design and ux choices (which I didn’t). I must say I severely underestimated the complexity before I started implementing this (supporting Dutch, Belgian and German addresses).
@mia Maybe it could provide adapters to a few common services and then devs have to supply their own API keys or whatever?
@jaredwhite yeah, but you're probably not exposing your api key on the front-end, so devs have to provide their own backend as well?
@mia @jaredwhite I would expect the component itself to have a solid interface to support the expected features. Any special api specific features could then have a wrapper to translate the data... Outside of an api key. It would require a bit of extra work for application to tie into the events, but still better than creating a whole component from scratch.
@mia @jaredwhite seriously, a component putting together the form fields for a shipping conforming to iso 19160 and iso 20022 would probably make the world a bether place. I’m quite sure I have not seen a correct one (except the company does shipping like ups/fedex/dhl/…).
Of course standard specifications should be accessible to everyone and free of charge!
