MingerWeb
Minh’s Notes Archives
On scrapping the Standalone: Part 2
Last Sunday, I commented on Adobe’s plan to scrap the Adobe® Atmosphere™ Standalone Player. Today, I have what could be a solution:
- Adobe would continue to produce the standalone Player, the Browser plug-in, and the Builder.
- Adobe would market either the Player or the Browser, whichever Adobe thinks has the most potential.
- Adobe would produce two packages, or
solutions
, one of which would focus on the Builder and Player, the other of which would include the Builder and Browser. The earlier package would be useful for those who would like to distribute games based on Atmosphere and for educators who would use Atmosphere in a virtual classroom environment, not as part of a website. The latter package would be useful for those developing websites, as they could embed Atmosphere content in the same manner that they now embed Macromedia Flash or Macromedia Shockwave content.
This plan would create flexibility to the project, making it easy for the Atmosphere technology to reach and serve all those interested.
I would also like to see the Atmospherians community develop more communities, each set to a particular type of niche in the Atmosphere user base. In addition to Community world and Town Square, Atmospherians could produce more high-quality worlds that would include occupiable buildings. There could be a Lake Eastwood neighborhood for personal worlds, a Canvas District for art galleries, an Arcade District for gaming worlds, a Downtown for commercial worlds, an Eastwood Elementary School for educational worlds, a Museum Row for museums and large art galleries, and so on. And these are just examples. But each would would have a particular category of tenants. And each world would have a specific name, as opposed to the generic names of current Atmospherians worlds (Community, Pro Builder World, Gallery, etc.). Well, I hope someone important at Adobe or Atmospherians reads this. ☻