We recently unveiled our #HashTapMap application that allows client to map user content (photos) generated through Instragram, Twitter, directly (via uploads), or potentially other social networks. Because of the complexity and performance issues associated with collecting and displaying content from multiple social networks and because of the broad range of price sensitivity associated with the markets we play, we realized that a “one-size fits them all” approach doesn't work well. As a result, here is a list of approaches and options available when it comes to the #HashTapMap.

A. Set Number of Location (Location-Driven Approach)

1. This approach centers around a fixed number of cities/locations in the United States (or world), usually associated with a tour or event. Because the number of locations is fixed, this approach is less expensive (approx. 30%), easier to control (aesthetically) and easier manage.
2. Aesthetics and control are not issues, and since this approach usually centers around promoting specific venues or events, is supported well by this model. Content found within these areas is aggregated under a single dot for that location. Content outside these locations is either ignored or placed into a segment containers (different color dots) usually at a state or metro area/city level.
3. By default, direct upload is supported and associated with the city/location the user chooses to upload content to. By default, user information (such as name) is not collected and location information is not verified (although this is possible using the user's IP address). Uploaded content is generally held in a queue until a Metablocks moderator has approved it. This cuts down on any abuse associate with the feature.
4. The benefits of this approach are: lower cost and faster implementation time, near real-time ability to update content (because of fewer locations, takes less time to update them), improved aesthetics and usability (fewer dots make them easier to navigate and gives you great visual control of your promotion)

B. Unlimited Number of Locations (Content-Driven Approach)

1. In this approach, content is pulled from across the United States (or world) and is mapped based on its actual location, regardless of where that may be.
2. Aesthetics and segmentation are key issues with this approach. Imagine, for example, thousands of dots randomly placed on a relatively small map area. Dots will soon overlap each other. Navigating to specific pieces of content becomes difficult or impossible. The resulting maps may look unattractive, complex or confusing. These are common issues that can arise when trying to map content from an unlimited number of location that clients need to be aware of. The #HashTapMap application gives client the following options to deal with this problem:
1. Doing Nothing: This is the least expensive option, but gives client very little control over how the map looks like or if the content density interferences with access or navigation. If you don't expect a huge amount of content being aggregated, this may be the way to, and you can always switch to another option when and if content density becomes a problem.
2. Using Segmentation: This is most expensive option because it involves breaking up the entire map into small segments and then grouping content using these segments. Content in the same segment appears and is accessible through one dot as opposed to multiple dots. Segments can range from states, to key cities/metro areas to much smaller units. The smaller the unit the more expensive the potential cost.
3. Using Moderation: This is essentially a mix of the first and second options, but done using our moderators. Maps are allowed to grow until content density becomes a problem and is then addressed and controlled manually to ensure the application aesthetic qualities and usability is kept intact.
3. By default, direct upload is not supported, unless client desires that uploaded be placed using geo-location information associated with a user's IP address. There is some added complexity (thus cost) associated with this option.