2 ms·

Thanks, I really appreciate the feedback, and they're totally valid points. I think you're right about the web app -- I've already built the "web-app" worldwid

by sjm 10y ago

Thanks, I really appreciate the feedback, and they're totally valid points. I think you're right about the web app -- I've already built the "web-app" worldwide preview, meant to tease you into getting the app, but there's no reason that couldn't be a functioning version of the app, similar to how it is now, but with the localisation working as an option if users allow the location request. I have a few ideas to slightly pivot if this doesn't really work, or take off the way it needs to succeed, and concentrating around the web app for Android users in the mean-time is a great idea.

brudgers 10y ago
To me, localization isn't a first order function. Just something Apple is in a position to demand of every app. Sure there's a scale at which it probably matters for some apps. Other than choosing ASCII, it's hard to accumulate significantly more technical debt without it than by building it in the MVP...actually because sunk costs create inertia, there might be more technical debt building it in up front than leaving it out. Or another way, IP address localization is the least effort that might possibly work. There are more corner cases, but the expectation of a web app in regard to location are lower than for an iOS app and if the rest of the system is good, users are likely to ignore it.