Building a better user experience is a paramount of concern for developers and designers alike. The need for a product to be simple, fluid and full of eye-candy can’t be understated. But with everything there are elements within a build where there may not be a solution that’s effective enough one of which is the multitude of times we as users have to add in address information during registrations, payment gateways and in various settings.
Coddress believes the burden of this specific portion of a users experience can be greatly reduced with their new address platform – making every circumstance of entering addresses easier and faster. The small three-person team from South Korea sympathizes with the inconvenient of having to consistently enter address information and have developed a solution to help improve these problems.
Besides registration difficulties of adding addresses, the Coddress team believes their expedited addressing service will have a strong impact when using overseas services. Due to different addressing systems in various counties, Coddress developed custom input solutions for distinct areas, which converts accordingly when implemented into a site. Currently Coddress is working with 30 countries with expansion imminent.
Thirdly, Coddress hopes with a greater user base navigation and address handling will be as simple as entering a name instead of inputting city or road names. A highly effective use case but requires acceptance and demand of usage of their service on various popular platforms to make this happen.
Users create their own Coddress on the platform, saving it for use when you visit various sites. But the real impact and usefulness of Coddress is when developers begin to use the service within their own code. With an API the solution becomes easy to implement and lets users simply add their Coddress “name” into the created input field, which then automatically fills the open fields accordingly for processing.
Would such a service make sense to implement as a developer for a startup? Without a large user base for the product should services begin adopting the service or should we as users build our own Coddress’ and hope developers see the need for implementation to build a better user experience? A bit of a chicken and egg situation but if users demand services for quicker and faster address labeling into platform forms services such as Coddress could take off.