With regards to the Infinite wall (I haven’t seen the issues you have mentioned, but can guess at the problem). As the stated point of the infinate wall was to have a wall that would guarantee that people could interact with at least one wall, why not either
a) Scrap the infinate wall and allow users to always see their closest wall.
b) Only allow users to see the infinate wall when there isn’t any other wall around.
c) Limit peoples posts on the infinate wall to 1 per hour or something similar.

I like the idea of very small radii walls, but can picture it being very frustrating. Perhaps let users know that there is a wall in their general vicinity without letting them access it until they are close enough.
Maybe give a distance to the wall which will allow people to move around until they find it, perhaps making this an option on wall creation.

Finally, what about an online map so that you can see if their are any walls in your area, or somewhere you are planning to visit.

Cheers
CC

Walls are viewable if the intersect my designated radius (not just the radius the phone is returning, of course).

Just some initial thoughts on this issue.

Great stuff Anoop - keep this thing rolling!

Thus, maybe the distance should really be left to the user creating the wall? As showed in your release 3 video, when you hit the “create new wall button,” there’s really not much to that screen besides entering a name for the wall. How about an option to choose the circumference of the wall based on the exact location provided by the GPS? That’ll give users in much broader places like parks and airports an option to spread their walls far and wide, but also give people the option to share restaurant information with people who are actually there.

That leaves the whole “what about the iphone 2g users?” Well how about also including the option to access google maps, triangulating and then doing a pin drop at your exact location, thus telling the phone the exact longitude and latitude that you’re at, making it as accurate as gps with the 3G.

That may be a bit of a stretch, and you may not even be able to access google maps through the software provided in the SDK, but I feel that iphone 3G users are the primary users of this app, and as such, we’re all really craving the walls to be very accurate to truly make this app as awesome as it can be.

I hope this helps?

That way, in sparse areas, I still have a good chance of seeing some walls, and in dense areas, I’ll see the walls that are closest to my current location.

Particularly for larger areas like airports, neighborhoods, and so on it’s nice to have the larger radius, and the sorting would kind of give people an intuitive sense of which walls are more relevant to their current location.

In any case, advice is often worth what you paid for it, so… But, great idea and execution.

Having said that, I believe that you should reduce the radii dramatically that a user ’sees’ when looking for walls. While it is difficult to tell from your post, I would presume that you should have control over what radius is actually used versus what radius the phone wants to use - maybe I am missing on that point.

But as your example shows, a wall that is five miles away from me isn’t local at all - which really eliminates the usefulness of this application. You have stated you don’t want the radius to be ten meters - fair enough - but I think 1000 is a much too large area.

I would suggest 100, maximum. If walls are truly meant to represent what is in my immediate area then anything much larger than this makes the point moot.

Anyways, I will stay tuned to see what you decide to do.