| Gave it a try on W7/64 Chrome. I happen to live outside hipster nation, so it took a while to load stuff. It did OK at letting me know this was in progress, but it could have been better. Had I not been reviewing it, I might have abandoned it. Going to the second page of items took longer than it should have. Returning to the site, it seems to want to start over acquiring the location. Can you not insert some memory for place in a first-party cookie? The place-locator button won't turn green unless the place is spelled perfectly. It's case sensitive. You might rethink the "generic" language shown to those who decline fb / tw access. Of course, if your monetizing scheme requires access to those services, maybe you're doing the right thing. I live in a place with lots of summer visitors, but right now it isn't summer. Data-wise, it seems to repeat items when there aren't enough items to fill its UI. Maybe it's only fair that there should be lots of dunkins and starbucks on line; there are in real life. But it's a little hokey looking. The Google Maps placemark (red ice-cream-cone with rectangle in it) is recognizable. It looks like an affordance to get to a map. But it isn't. The scroll-in Click To Expand does exactly the same thing as clicking on the picture or the placemark, as far as I can tell. Also, the cursor doesn't change anywhere within a place listing. Lost opportunity for UX depth? Thanks for the chance to review this. All the best. |