MashupBusinessInhibitors

From MashupCamp

Business Inhibitors for Mashups

• Mashup Advantages
  • situational applications- if long lived and popular, make it into an application
    • mashup allows prototyping of applications
  • mashups add space and time aspects to tabular/text form of data

• How do businesses make money?
  • understanding economics of abundance vs. scarcity
  • content subscriptions (sell info)
    • ex. accuweathyer- sell analytics- predicting storms. Tiered solutions
  • advertising
    • API defeats advertising model- most content providers are advertising based, need to balance pushing advertising with content
  • selling aggregated info on users
  • bartering assets - widgets, data
    • how to formalize, needs to be very social- agreements between developers
  • sell tools vs. content

• Credentials
  • managing multiple credentials to different service providers- need a common identity model
  • if credentials are required to access info, what about search engine indexing etc.?

• Content providers
  • How much information to share with feeds? When should users have to come to the site? teaser vs. full feeds
  • monetizing information- subscription/advertising/etc.
  • internal vs. external feeds- now require different tools
  • commercial vs. noncommercial use of content
    • define "commercial" when does a corporation testing/trying out/developing a product become commercial?

• Culture
  • mashups don't fit development model- Web not acknowledged as a platform by traditional IT
  • no pool of widgets/feeds/etc. so need to pull in IT
    • but hard to prove to IT that this is a valid model
  • open source community can provide feeds/widgets, but right now no community
  • amateurs vs. professionals- amateurs can't wait, professionals question reliability
  • different programming model, slow adoption process- different tools, standards, best practices
    • different users
  • traditional IT- business based on scarcity, now abundance of info/content
    • IT safely enable users to do what they want/need, but need to enforce making it safe
    • IT control culture
    • IT provided internal data as a service-needs to be centralized and controlled
  • legacy inertia - It folks "this will pass"
    • Data as an IT resource instead of a corporate resource

• • • many different licensing arrangements for data
  • IT inhibitors- IT professionals don't own content, not even web 2.0 accessible (no feeds...)
  • make propriety data available- can only use for your company
  • for display only, no consumption in an application
  • free distribution
  • how long can you keep data? can you store it?
  • data license and copy write
  • data hard to track
  • vague terms of service- risk will get sued for using this?

• availability of data in consumable format
  • right not google maps and RSS feeds
  • Dapper, Kapow

• bringing content providers, developers, and mashup users/assemblers together

• green taxes- companies need to know what exposure is- what is the risk w/ this product?

• screen captures-some content providers prohibit screen captures (ex. Google maps)

--Meg.sorber 15:58, 19 July 2007 (EDT)