My new startup Timu officially launches
Yesterday was a big day for me, after 8 months of planning and product development work finally launched my new startup, Timu. Timu gave me a chance to apply many of the lessons learned with designing and building ActiveRain to another market, amateur sports.
It's a social networking platform specifically built to solve the communications problems encountered by athletes, sports teams and their fans. Online social networking is a natural way to solve many of these problems. Yet, existing social networks provide disjointed solutions that do not handle sports specific features, such as player rosters, game results and statistics. At the same time existing sports web site offerings provide little interactivity and user engagement.
Individual athletes can setup an profile on Timu in minutes. Profiles can be customized with information about the sports they participate in, teams they play on, and their competitive highlights. Photos, videos can be uploaded, and various “widgets” can be added or modified. These profiles serve as one center of communication within Timu.
Coaches, players, or parents can create a team center for your team on Timu. Team centers provide many features like team news, schedules, player rosters, photos, game results, statistics, statistics and a wide range of commmunication tools. All of the people associated with the team can be invited to become members of the team center, which can then function as a hub for team communications.
A few examples of team centers: http://bellevueblaze.timu.com http://dreadsox.timu.com http://baseball.timu.com
Currently Timu supports about 30 different sports ranging from baseball and soccer to unicycling. Each of these sports has it’s own section or hub on Timu including photos, videos, game results and discussions. Timu members can participate in the conversation at these hubs about their sport. As Timu grows we will be providing the ability to view these hubs by region, subsection of a sport, or even by sporting venue.
Comments (2)Subscribe to CommentsComment