Main Subject
#1 in Business Subscribe Email Print

You are here: Home > Business > Marketing > Apollo, We Have A Problem

Tags

  • desktop
  • various
  • companies
  • developing combination

  • Links

  • A Dangerous Temptation - The Lure of Hating Back, Hurting Back
  • Why Blog
  • Constructing Screenplays: Forrest Gump (1994) Deconstructed
  • Main Subject - Apollo, We Have A Problem

    Funny how my mind works. When I read that Adobe was releasing an early version of their Apollo application platform, all I could think of was how the original Apollo
    According to USFDA, a combination product is one composed of any combination of a drug and device; biological product and device; drug and biological product
    of Mount Olympus fame spread a virus. The fact that Apollo killed a Python in Delphi only adds a multitude of unintentional software humor.

    From a technical standpoi
    ; or drug, device, and biological product and fixed dose combination would include two or more combinations of drug.

    Examples of combination products may in
    nt, Apollo is interesting, though from a marketing standpoint it is of questionable survivability. Technically, Adobe is simply making web applications standalone des
    lude drug-coated devices, drugs packaged with delivery devices in medical kits, and drugs and devices packaged separately but intended to be used together.

    top apps by localizing HTML, Flash, and other common web goodies into a self-contained, platform-agnostic system. Pretty slick approach given that people already devel
    here is enormous increase in the number of combination products entering the market in the recent years. Combination products have proven advantages but fixe
    oping web-based applications have low learning curves to create portable desktop apps.

    However, the application development heavens are an unforgiving place. The gods
    d dose combinations are still in the process of convincing regulatory authority on their advantages over the single ingredient formulations.

    Combination pro
    therein (Microsoft, Java, LAMP, etc.) are ill tempered and unlikely to yield followers. At this point in development theology, there are too many gods, mortals that ar
    ucts have become life saving products for the pharmaceutical companies who doesn’t have many innovative molecules in their product pipeline and have been inc
    e too devout, and few new disciples to whom evangelism will work.

    Rare is a development organization that can afford to change their technical base. Small shops canno
    easingly used in the product life cycle management. Even the companies having product patents are trying to extend their product life cycle through the combi
    afford the learning curve to adopt new development languages, and large ones have implemented long-term platform strategies for which they are oath to abandon. Howeve
    nation products and maximize the revenues. But the companies involved in this practice are overlooking that they are burdening the patients both economically
    r, change does happen. Not long ago Java was a toy, and yet it has become a dominant force in server-side and web based enterprise application and e-commerce developme
    and physically. They need to rightly judge the benefits of the combination products and they have to even look at the risks involved when combining the produ
    t. Microsoft still holds the power on PCs as Windows still dominates the desktop. Thus Apollo will have to ride in the sky a long time before finding a landing place
    ts. Some of the combination products were well accepted by physicians while others suffered. Companies involved in development of combination products are fi
    on technocrat terra firma.

    The base question can be summed up "Does the market need yet another development platform?" Granted, cross platform agility within a famili
    ding difficulty in defining their combination products and facing various challenges from selecting a combination to marketing it.

    Following aspects would a
    ar framework and end user interface is compelling. But the switching cost is high, and the non-Windows installed base is small. Adobe may be laying an egg in hopes th
    dd to the challenges in developing combination products:

    Which markets to tap where the combination products can do fairly well?
    Which combination prod
    t the chickens will soon arrive. That however is a questionable strategy.

    This situation should be familiar to anyone in technology marketing. Adobe is faced with cr
    cts are meaningful and rational?
    Which therapeutic categories to select?
    Which Combinations can address unmet needs of the patients?
    Do combin
    eating a following within a saturated market (the software development market is by quirky definition saturated from the start as anyone who wants to develop software m
    tions increase the patient compliance?
    What would be the developing cost?
    How to tackle the risks encountered during combination product developmen
    st either know and love a programming language and platform, or they must careful pick one appropriate for their product). Adobe has several things going for them:

    *
    t?

    As combination products don't fit into the traditional categories of drugs, medical devices, or biological products, the USFDA is in the process of devel
    They are repackaging well known and well loved development tools that already have followings.

    * They have a compelling cross platform story for new projects.

    * Adobe
    ping new procedures for reviewing their safety, efficacy and quality.

    Professional from academic institutions, pharmaceutical industries, health care indust
    is a well liked and trusted vendor (unlike the Evil Empire ).

    Yet they face significant barriers to entry:

    * High switching costs for most technology buyer genotypes.
    y and representatives from various regulatory agencies are working out to design the regulatory requirements for manufacture and sale of combination products


    * Compelling competitive ROI for Open Source alternatives.

    * Innovative competitors like Brainwave who offer the same gestalt.

    * Fear of vendor lock-in amplified by
    .

    As there is an increasing trend of the combination products companies manufacturing such products should be able to tackle the problems involved in the de
    Open Source alternatives.

    Adobe has few options in acquiring tractions aside from a market seeding campaign, and ploys to CTOs about extending their existing in-house
    elopment. They need to be wiser in analyzing the market trends and the regulatory requirements.

    Companies that provide selfless information through particip
    expertise in web technologies to work on desktop solutions. If Apollo is to fly, it will have to whip the chariot horses hard and beware the jealousy of the other gods


    tion in industry events and feedback to regulatory authorities would be able to face the challenges and will be successful in developing combination products

    HTTP = HTML link (for blogs, profiles,phorums):
    <a href="http://www.mainsubjects.org.ua/article/25709/mainsubjects-Apollo-We-Have-A-Problem.html">Apollo, We Have A Problem</a>

    BB link (for phorums):
    [url=http://www.mainsubjects.org.ua/article/25709/mainsubjects-Apollo-We-Have-A-Problem.html]Apollo, We Have A Problem[/url]

    Related Articles:

    The Meaninglessness of Ford Motor Company

    Does Your Organization Have a Learning Disability - Disability # 5 - Slow Change Kills

    Where Businesses Fall Short

    Bookmark it: del.icio.us digg.com reddit.com netvouz.com google.com yahoo.com technorati.com furl.net bloglines.com socialdust.com ma.gnolia.com newsvine.com slashdot.org simpy.com shadows.com blinklist.com