Dumbing-down Mashups. A Good Thing?

I’ve been heads-down on some projects lately, and if I still didn’t manage to peek up and check some of my favorite sites, I might have missed this news about Dapper via ReadWriteWeb. <embarrassment>I had no idea Dapper had been acquired by Yahoo last week</embarrassment>

They were one of the original “do-it-yourself” API tools a few years back before switching their model to contextual advertising. I wasn’t thrilled to see the change in focus, but at least they kept Dapper up and running.

 Marshall Kirkpatrick has written an excellent article about discovering Dapper, and the effect it had on him. He barely mentions “mashups”, but you get a great sense of how empowering the technology was for him.

He also mentions NeedleBase in passing, a free hosted tool that I admit I haven’t used much. In practice, it sounds very similar to Connotate, a commercial mashup product whose “Intelligent Agents” learn what to scrape by example. Alas, NeedleBase is a product of ITA Software, a travel search/software firm that was acquired by Google back in July. The product is still available, but Google doesn’t exactly have a good track record in the mashup space.

I see a clear trend away from “mashups”, and towards “data harvesting”.  Marshall’s uses of Dapper are clearly in the “Harvest” category, and NeedleBase describes itself as “a revolutionary platform for acquiring, integrating, cleansing, analyzing and publishing data on the web”. Even venerable Kapow Technologies no longer mentions the word “mashup” on their homepage, but you can read plenty about acquiring data from the web.  

What does it mean? Marshall makes a good argument how about technology that is too innovative for the current marketplace often doesn’t gain the traction it needs to succeed. I think we are seeing a slight “dumbing down” of mashup technology/terminology to a few simple use cases that people can easily grasp. Once they understand how these tools can give them easy access to a wealth of new information, they will start combining the various pieces and “mashups” will finally gain broad acceptance as a solution paradigm.

But that’s just the path for the teeming masses. If you’re reading this, you’re probably ahead of the curve and looking beyond scraping to mashups’ more powerful capabilities. Most firms have barely (if that!) begun to exploit the potential of mashups, and I see that as a chance to gain a competitive advantage. You can wait until mashups are mainstream (again) or you can use this time to build an enterprise app store, create propreitary information streams, and make your IT department more productive. Will you wait until your peers seize this opportunity, or will you use this time to jump ahead of them?

2 Responses to “Dumbing-down Mashups. A Good Thing?”

  • Michael,

    Reading your comments has really reinforced some of my own thoughts after working with mashups now for more than a year.

    As an aside, Dapper was fundamental in building my first real business mashup, one which we still use today. I’d be disappointed if Yahoo discontinued it.

    Mashups still seem to be so poorly understood and much of the industry “chatter” seems to have refocussed on social media and e2.0 and the true potential of mashups and the attendant apps still hasn’t reached the right ears.

    A quote from an interview with Oscar Berg commenting mainly about intranets seems entirely applicable here: “Perhaps the new role of IT is work with the business to bring out the magic that technology makes possible.”

    I think we need to show the business the “magic of mashups” and the potential they offer.

    I also believe the greatest future opportunity lies in the use of mashups and apps for Business Intelligence. Unfortunately, the greatest impediment at the moment seems to be a lack of “digestible data” that’s easy for business users to grab, mash, and display in dashboards.

    I am still completely won over by the opportunities for mashups. I only wish I could dedicate more time to promoting the “magic”.

    Thanks for your thoughts.
    Innes

  • […] popular and tens of thousands of these tasks have been created by the community. As I wrote in my post, “Dumbing-down Mashups: A Good Thing?” the spread of simpler mashup products like ifttt is […]

Leave a Reply

  • BusinessUSA Data
    The BusinessUSA Data API allows users to access data asset information provided by BusinessUSA for current or prospective business owners. The BusinessUSA Data API uses a resource URL request and provides return response in CSV, XML, and JSON. Authentication is completed through a unique, private API Key. BusinessUSA is an official United States Government website […]
  • Flurry EventMetrics
    Flurry EventMetrics API provides the ability to request event information for applications. Requests are made in XML and JSON format using an API access code and provides XML or JSON responses. Flurry is part of Yahoo Developer Network and is a mobile apps analytics platform serving over 60,000 companies in over 150,000 applications across iOS, […]
  • Zillow Property GetDeepSearch-Results
    The GetDeepSearchResults API aims to find a property for a specified address. The objective of the result set returned is to have the full address(s), zpid and Zestimate data that is provided by the GetSearchResults API. The API call also returns property data like lot size, year built, bath/beds, last sale details etc. Date Updated: […]
  • Zillow Neighborhood GetDemographics
    The GetDemographics API aims to return a set of market, affordability, real estate, and demographic data for a specified region, including: Local Market Data (e.g., median list price, number of homes for sale, percent listing price reduction), Affordability data (e.g., Zillow Home Value Index, 1-Yr change, property tax, etc.), Homes and Real Estate data (e.g., […]
  • Zillow Mortgage GetRateSummary
    The GetRateSummary API allows developers to access the current rates and the previous weeks rates per loan type from Zillow Mortgage Marketplace. Current supported loan types are: 30-year fixed, 15-year fixed, and 5/1 ARM. The GetRateSummary API aims to return rates for a specific state if the optional state parameter is used. Date Updated: 2015-02-27 […]
  • Zillow Mortgage GetMonthlyPayments
    The GetMonthlyPayments API aims to return the estimated monthly payment that includes principal and interest based on today's mortgage rate. The goal is to return the estimated monthly payment per loan type (30-year fixed, 15-year fixed, and 5/1 ARM). If a ZIP code is entered, the estimated taxes and insurance are returned in the result […]
  • Zillow Neighborhood GetRegionChart
    The GetRegionChart API aims to generate a URL for an image file that displays the historical Zestimates for a specific geographic region. The API's objective is to accept the region as well as a chart type: either percentage or dollar value change. Optionally, the API accepts width and height parameters that constrain the size of […]
  • Zillow Property GetDeepComps
    The GetDeepComps API aims to return a list of comparable recent sales for a specified property. The goal of the returned result sets is to list the address, Zillow property identifier, and Zestimate for the comparable properties and the principal property for which the comparables are being retrieved while also returning property data for the […]
  • Zillow Property GetUpdatedPropertyDetails
    The GetUpdatedPropertyDetails API aims to return all of the home facts that have been edited by the home's owner or agent. The objective of the result set is to contain the following attributes: Property address, Zillow property identifier, Posting details such as the agent name, MLS number, price, and posting type (For Sale or Make […]
  • Zillow Neighborhood GetRegionChildren
    The GetRegionChildren API aims to return a list of subregions with the following information for a specified region: Subregion Type, Region IDs, Region Names, URL to Corresponding Zillow Page (only for cities and neighborhoods), Latitudes and Longitudes, A region can be specified at various levels of the region hierarchy. An optional childtype parameter can also […]