Showing posts with label ajax. Show all posts
Showing posts with label ajax. Show all posts

Sunday, June 3, 2007

Differences of 2.0's

A lot of people ask us here at JackBe about the definitions and or differences between Web 2.0, Enterprise Web 2.0 and Enterprise 2.0. So here are some of my thoughts simplified for a blog post.

Web 2.0 – There are two parts to this one which will make sense when I get into the difference between Enterprise Web 2.0 and Enterprise 2.0.

1. Web 2.0 – the user-driven paradigm shift. Youtube, blogs, wikis, RIAs with greater self-service capabilities… all of these are examples of a paradigm shift from older HTML static, mostly one way communication of ideas and information to a new User-Driven web model which enables you and me to more easily contribute content, share information and collaborate with each other through the web.

2. Web 2.0 - technology enablers. This user-driven shift has been made possible in part by new or now accepted technologies and techniques which have gained greater penetration as web application tools. Such include: Ajax, proprietary RIA tools like Flex and Lazlo and now Silverlight, Service Orientated Architecture (SOA), Ruby on Rail and other lightweight dev models, Web Services like REST and RSS, Mashups (data and visual) and Tagging. Of course this is not an exclusive list but I think you get my point.

Enterprise Web 2.0 – the Web 2.0 technologies mentioned above put into practice in the enterprise. For example: richer, more productive customer self-service apps, inter-department collaboration through bogs, and wikis. But simply ‘slapping’ these technologies into a rooted organization will not bring about the same successes and value that Web 2.0 apps have enjoyed in the public domain. Enterprises have too many constraints and need a mind and culture shift along with deep embedment of these 2.0 tools into its processes to have any kind of a definable impact.

Enterprise 2.0 – The Enterprise 2.0 is analogous to #1 above in that it represents a user orientated paradigm shift of the enterprise makeup itself. It embraces the decentralized organization built around disparate data and information with users empowered to create new information built around and on top of others ideas through sharing, and collaboration. An organic organization loosely designed and constructed to empower knowledge workers to do what they do best by giving them what they need, when the need it and how they need it by enabling them with 2.0 technologies and nurturing this new paradigm mind set internally. Here enterprises reap the benefits of 2.0 through network effects from its user’s contributions and collaboration and realize success that increases proportionally as more users contribute to the organism creating a potentially indefinable value proposition to stakeholders.

Each of these could be expanded in much more detail but why make it more complicated as this? If you have any thoughts please feel free to share or contact me. That is after all the point.

Read More...

Monday, April 9, 2007

The Copernican Software Revolution ("Users are the Killer App")

Web 2.0 technology continues to shine the light on users. Luis Derechin, JackBe CEO, and I spoke on this topic several weeks ago at the AjaxWorld 2007 event in NYC in a presentation entitled "The User is the Killer App". I've been so busy working on getting Presto, our Enterprise Web 2.0 Platform and Mashup Environment out the door that I've been remiss in my blogging...well, I couldn't help but follow up on our talk with some comments, since I feel so strongly about the evolving role of users in every facet of next generation software.

Let me make the my point with a little review of history: In the year 1543, in what was considered a very controversial proposition, the Polish-born scientist Copernicus published a theory contradicting long-held views and conventional wisdom, proposing that the Sun, not the Earth, was the center of the Solar System. Such a model is called a "heliocentric" or sun-centered system.

In the Universe of software architecture over time we've seen numerous discussions focus around server-centric and client-centric architectures. From mainframes and dumb-terminals through the 1980's (server-centric), to Client-Server in the 80's and 90's (more client-centric), to Web-based in the 90's and into 2K (back to more server-centric), and RIA/Ajax-based applications today (back to more client-centric).

I think focusing on client or server in this equation is missing the point. Sure, the pendulum swings back and forth between the relative importance of client and server, but the pivot point from which this pendulum swings remains unmoved above...Imagine this pivot point as the user! Successful software must focus on the User, an approach best termed a "user-centric" or user-centered system.

Software should be user-centered in it's design and development, user-driven in its approach to integration and empowering in its collaboration models and support for ad-hoc, situational applications and mashups.

The evolution of User-Centric Software:

Last year I had the privilege of hearing Mark Hurst, Founder and President of Creative Good, a premiere User-Experience consulting firm, present on customer-focused strategies and he touched on a similar topic. Mark made the point that companies often fail to realize that the customer is the center of their universe.

As we’ve matured as technologists, our industry has continued to adopt a more user-focused approach to software development, an approach referred to now as Agile software development. Extending this focus even more broadly to create more “user-centric” and “user-driven” software is the next step in this natural evolution.

The term “Web 2.0” means different things to different people, but all definitions include one common theme: a strong focus on users. Consider the following features of the next generation of web software :

  • User-driven content: the user of the software having more control over what data sources are utilized as part of their applications. It also implies more dynamic access to these data sources.
  • User-driven selection/configuration: the software having more control of how information is labeled, categorized, as well as content layout, filtering and look and feel.
  • User-driven integration: the user having more control over how various, disparate data sources are combined and transformed as well as how these data sources are utilized and manipulated within an application.
The overall emphasis is on a very dynamic user-driven model.

As we like to say at JackBe: "Users are the Killer App"!

Read More...

Friday, March 30, 2007

Ajax Meets RFID

Like every solutions provider, JackBe tries very hard to share practical uses of its software and real-world success stories. I recently got a note from one of JackBe's Project Managers, Dr. Jerrold Prothero, and I thought it was a great example of Ajax 'moving beyond the technology' and moving into real-world business use:

This week, the RFID industry is holding its major conference, RFID World, in Dallas. You’ve probably heard about RFID. It’s basically “barcodes on steroids”, the next generation of product-tracking that is currently revolutionizing the supply chain industry.

RFID allows product information to be read automatically in bulk from a distance. For the first time, it makes it practical to get detailed, real-time information about where things are as they move from manufacturing through distribution to retail outlets. RFID dramatically increases supply chain visibility. And the technology is now in mature adoption, with RFID tag prices having dropped 60-70% over the last 12 months.

An intriguing new marriage is now starting to emerge between RFID and Ajax. RFID makes product information available; Ajax makes it possible to visualize and interact with this information over the web. IBM gave an RFID World presentation, 'Edge Computing Platforms - Innovative Capabilities through Item-Level Visibility' that discussed this theme and referenced JackBe software as an example of what is possible.

When you think about it, the potential for enterprise-grade Ajax environments in supply chain applications is huge. Products such as those developed by JackBe promote the ability to maintain situation awareness, by supporting rapid configuration and presentation of live data feeds; information sharing, by supporting a secure common workspace for information display; and collaboration, by supporting information update with governance controls. All of these issues are critical for the supply chain industry, with its reliance on extensive and fluid partnerships spread around the world.

Ajax and RFID. Let the games begin!


Of course, a short blog post probably doesn't do this topic justice. If you'd like to chat more on Ajax and RFID, you can reach Jerrold at jerrold.prothero@jackbe.com.

Read More...

Monday, March 26, 2007

The Fifth Level of Ajax

I think that all Ajax vendors have been touting the benefits of 'improved user experience' as their value proposition for a while. The problem with this proposition is that it is very hard to quantify.

But, they are missing something. It isn't just about the "experience" but about empowering the user with a better view and access to any data source. Consider the "Four Levels of Ajax Adoption" from Ray Valdez at Gartner. Ray has said that the levels are:
  1. Snippets
  2. Widgets
  3. Client Framework
  4. Client-Server Framework
I think Ray is missing the next level. The 5th level should be 'User-driven Framework', a framework that has all of the benefits of level 4 but allows the user to be the one pulling and mashing any information that exists in the enterprise, the trusted partner's enterprise and the Web. This may seem to be a small difference, but in reality it is the difference between 'improved user experience' and 'improved access to information which gives the true competitive advantage'. And to most business users, that's an important distinction.

So, we suggest the 'Five Levels of Ajax Adoption' :
  1. Snippets
  2. Widgets
  3. Client Framework
  4. Client-Server Framework
  5. User-Driven Framework
JackBe has embraced this idea through its new products, Dash, our dynamic interface for user-driven mashups, and Edge, our virtualization and mashup server. This is an emerging area and one we'll be talking about a lot in 2007.

Read More...

Thursday, March 22, 2007

Ajax: Our baby is growing up!

Well, the craziness that is AjaxWorld East 2007 is over. But it was crazy in a good way. JackBe was a sponsor of the event for the second time and it was certainly worth it. It was a very well-run show and certainly a good example of how a well-executed and focused event can positively influence the growth and evolution of a technology and an industry. Jeremy, Carmen, Megan, Lauren and the rest of top-notch staff at Sys-Con have our compliments. They certainly make every effort to create a worthwhile event for vendors and attendees alike. We hope and expect the recordings of the conference presentations (including 3 by JackBe execs) to be online within a few weeks. Bonus points to you if you can name any of the gentlemen in the pictures from the show.

My corporate take on AjaxWorld is that it is definitive proof that Ajax as a technology is certainly growing up and doing so fast. As one attendee put it, ‘our Ajax baby is growing up’. Many of the common concerns about Ajax in years past are now being addressed, including issues like off-line support, security, and real-time messaging. These deep-dive technical questions were nicely balanced by big picture questions about the kinds of solutions that have been implemented and the business benefits that resulted. I’d say that the Ajax industry is moving through its ‘gangly teenager’ years quickly and is already looking towards its future as an adult.

On a personal note, I must say it was great as always to have the chance to shake hands (and even drink beer, in a few cases) with founders, CTOs, and big thinkers from movers-and-shakers like Cynergy, Dojo, Tibco, Helmi,Backbase, and IceSoft. Sure, some are competitors and normally I’d prefer you didn’t even know they existed. But putting my competitive hat aside for a few seconds, I think this is one of the overlooked qualities of this growing industry: it is still very personal. You can meet them, pick their brain, and get a real feeling for the solidity of their technologies.

So, after all this, what's next for JackBe? The Web 2.0 Expo in San Francisco at the Moscone Center, April 15-18. This event isn’t focused on specific technologies like Ajax but more on the broad set of technologies/functionalities that sit under the ‘Web 2.0’ banner and the opportunities that they enable. Sticking to the Web 2.0 theme, we will be highlighting our work on Dash, our dynamic interface for user-driven mashups, and Edge, our virtualization and mashup server. If you are a west-coaster and want to come chat with JackBe in person at the Expo, we can help save you a bit of money. Go to http://www.web2expo.com/pub/w/53/register.html and, when prompted, enter code ‘webex07exb’ to get $100 off the normal registration fee. (If you are a student or government employee, there are other discounts available as well.) We hope to see ya there.

Read More...

Tuesday, March 13, 2007

Ajax is for real in 'Real-World Ajax'

There are a couple of new books on Enterprise 2.0 you may want to check out. First, from Sandy Carter at IBM, is ‘The New Language of Business: SOA & Web 2.0’. It's a good look at what makes SOA projects work. But more important, as Joe McKendrick at ZD Net points out, the book elevates Web 2.0 to true enterprise-grade status. I couldn't agree more.

But we'd would be remiss if I didn’t give equal time to ‘Real-World Ajax’, a substantial effort from our friends Dion Hinchcliffe and Kate Allen. This type of work just proves that Ajax is ready for prime in the enterprise. Once you read it, we expect you'll agree. (In the interest of full disclosure: Yes, we are a bit biased, as there’s a nice section in there on JackBe’s Ajax Bank demo.)

Read More...

Monday, March 12, 2007

Business Value Continued….Enterprise Mashups and Total Cost of Ownership Part 2

Well I’m back with some more ideas and thoughts about Web 2.0, the enabling technologies driving it, and the potential benefits for enterprises. I tend to focus on the technologies and the enterprise aspect of Web 2.0 simply because I get tired (am tired) of people defining it as simply a “social collaborative” movement. Although this is true, and great for my girlfriend who can blog and share her photos, this says little to the strategic impact that the underlying technologies, that make capable the social aspects, can have on the enterprise. Here are a few real universal business situations or rather timeless barriers to a better bottom line that technologies such as Ajax, Mashups, and a SOA can positively affect.

Quickly adapt to Changing Business Needs.

When organizations mandate a business process rule, such as a limit on the size of a particular type of business transaction, it is typically embedded deep within the application code. Finding, adjusting, and maintaining consistency with other systems can be error-prone and extremely time consuming and error-prone processes. By deploying such rules in a separate but integrated environment, organizations can empower business executives via a user interface to achieve extreme agility and oversight.

Effectively Monitor and Continuously Improve the Business

Systems information and transactional flows capture critical interactions that may be required for financial, contractual, regulatory, and business governance. Tracing and reporting audit data are tedious tasks and tenuously contingent on predefined conditions, including monitoring servers and client devices, coding predetermined subroutines to capture processing metrics, running batch routines for replication and reporting, and so forth. Due to the complexity of pulling this information together across a whole business process, the effort is often only made when critical issues arise. To avoid business risk, ongoing monitoring can be automatically captured by the abstracted process layer, which can trigger alerts, alternate process flows, provide automated reporting, and expose many other intelligence metrics. By reacting to early warnings a business can preempt situations that may cause undue and costly mistakes. Organizations may also seek to implement Six Sigma or regulatory initiatives via this type on mechanism.

Simplify Business Integration Efforts

Integration points that are incorporated and managed in close context to specific business processes will provide significantly more value. In the example, enterprise procurement activities are often scattered across multiple systems, where the collating, parsing, and regrouping of items to be sourced are typically very manual and labor-intensive processes. However, these processes can be centralized and automated into a composite application or mashup that avoids these inefficiencies.

Reduce Costs and Risks of Manual Processing

Many organizations still struggle trying to automate manual or paper-based transactions. Highly document-intensive composite application processes are very common targets for Web services. In the procurement example, a user may intervene in multiple places, introducing the potential to corrupt the process flow. With an orchestrated composite application, automated triggers engage users where and when necessary, removing the need for each individual to know every activity in the process required to continue the flow of a specific transaction.

Leverage Existing Systems and Resources

Reusability of code not only saver resource efforts in development and maintenance, it also impacts application quality and security. By utilizing a standardized framework, companies can focus skills development across a variety of systems and solutions to prevent these effects.

Again, these are just a few examples but I and JackBe believe it is these types of scenarios that are not as highly publicized at the moment (overshadowed by the Youttube/myspace buzz) but will at the end of the day drive real business value to the mass.

Read More...

Tuesday, March 6, 2007

Enterprise Mashups and Total Cost of Ownership

What is all the Web 2.0, Ajax, Enterprise 2.0, SOA buzz in the driving towards? What does it mean for the line-of-business manager or the enterprise itself? I thought I’d take a moment at breaking down how the approaches/ideas and supporting technologies could positively impact the underlying business books. As to not make this to vague, I’ll take the latest hallmark of Enterprise 2.0, Enterprise Mashups, and a classic financial benchmark Total Cost of Ownership (TCO), and we’ll deconstruct how this latest set of technologies and techniques stands up against an old benchmark.

The TCO of a solution must take into account the initial and ongoing costs of the solution, relative to the solution it replaces. Enterprise Mashups (which are closely related to composite applications if not the same depending on one’s definition) are based upon a SOA and have the potential to lower TCO in several ways, including:

  • Managing the Services in an SOA is less expensive and complex than managing the interfaces in a traditional integration solution.
  • By leveraging the Web Services standards, mashups can lower the cost of proprietary technologies. Standards level the competitive playing field for vendors by lowering prices generally, and also simplify the task of integration, lowering costs directly.
  • Business analysts and technical business users are able to compose applications without the involvement of more expensive IT personnel.
  • The more complex a business change is, the more effective SOA-based mashups can be at reducing the TCO of the solution because of their inherently flexible nature.

Fundamentally, a SOA provides business an “agility quotient” – the more complex the underlying infrastructure and the more dynamic the business environment, the greater the benefit of an agile architecture to the business. SOAs provide the ability for business users to create enterprise mashups, thus creating and managing business processes.

Where am I going with all of this and how does it fit into the world of Ajax, RIA, or JackBe for that matter? There is one important piece yet missing – the user interface itself. If the tools that users interact with aren’t agile themselves, the benefits of these enterprise mashups to the organization risk being lost. The services that contribute to a mashup can now be consumed by light-weight client models thanks to Ajax. This is why the integration layer will be driven by those who are experienced with client side models. The back-end can do their part, expose the services, which they have or are doing so, but they aren’t going to be able to create what is truly needed for the consumption because this is not there expertise. The services are moving out farther-the power of the apps as well-to the client so it only makes sense that the driver of this integration will be through the client tier experts and more specifically, those skilled in Ajax.

Later, I’ll attempt to address the benefits of incorporating SOA, Ajax, and Mashups into the enterprise to more strategic business benefits. Please feel free to leave your comments and opinions.

Read More...

Monday, February 26, 2007

Ajax Application Patterns

Since I think in Patterns and JackBe has done lots of Ajax in the last few years, I've tried to organize all the work we’d done as a set of Ajax application patterns. I was able to whittle it down to three:

  1. The first (obvious) pattern was simple: down-and-dirty Web Apps. Take any old client-server application, applications you need but haven’t gotten around to building, and new enterprise class applications and move them to the browser using Ajax. You’ve probably seen examples of this in the consumer world like self-service travel or account access & bill payment, and in the enterprise world, ‘SaaS’ apps like on-line CRM/ERP. We’ve even done this in one instance where the application was supposed to look exactly like its client-server predecessor. Admittedly, it wasn’t terribly sexy-looking, since the original app was many years old. The application owners wanted to deploy new features easily but didn’t want to retrain a workforce of 10,000+. They got the best of both worlds.
  2. A second (less obvious) Ajax application pattern is the Dynamic Desktop. You give users easy access to sources of data and logic, easy ways to integrate them, and easy ways to apply visual skins, such as graphs and maps. While this is certainly a popular style in the consumer world, enterprises always have higher requirements in areas like security, governance, and scalability. This application pattern works well in areas where knowledge workers have ever-changing information needs. Think call center staff or anyone with ‘analyst’ in their title. The coolest example I know of is the briefing dashboard we’ve developed for the DIA.
  3. Finally, the least obvious, but the one I think has the most potential is the 'Web Embeddable'. In this case, the emphasis is on embedding business functionality into a page as a black box. Pretty much like Google Maps, except for the enterprise. The Web Embeddable is delivered from the enterprise data center and all communication between it and the data center is handled out of the box. Many people might think I am talking about snippets and widgets like popup calendars and sliders. This is not that. Think about a mini home loan approval application. Instead of going to a LendingTree.com site to apply, why not have Lending Tree develop a Web Embeddable and syndicate it? Let anyone embed it and get a cut from Lending Tree. Seems to make sense to me (we call this Application Syndication). JackBe did this for a recent customer. We built an e-commerce checkout Web Embeddable that did full catalog and shopping management. The beauty is it doesn't care where it's running because all communication from the application to the data center is self managed and secure. This makes for a wonderful user experence and that is always good for business.
So, which Ajax application pattern have you used?

Read More...

Friday, February 23, 2007

Web 2.0 in the Top Secret world

One of JackBe's customers, the Defense Intelligence Agency (DIA), is spotlighted in Computerworld. It's a nice, concise summary of Web 2.0 technologies and their use within the highly-secure, high-demand world of intelligence gathering and analysis.

Sure, it's a bit self-serving to blog about one of our own customers in the news. But it's not every day that the generally-secretive folks in the intelligence community talk about the tools they use in their world. We're very proud of our work with them! And there might even be a few lessons you could learn from their work.

Read More...

Thursday, February 22, 2007

The Age of Customization: Enterprise Web 2.0 is the perfect pair of pants!

I spent last weekend searching for pants. I had a need. I looked for pants that were comfortable in the winter and summer but would always ‘breath’, the right material so they would last, and also pants that would be acceptable for multiple occasions. The problem is I couldn’t find a pair that met all these needs. I had to buy multiple pairs. I settled on the only solution that was available at that time. I will have to adapt the right solution (many pants) instead of having one solution (one pair of pants) that adjusts to my needs, when I need something different as situations arise.

I want a pair of pants that could change on-the-fly (no pun intended) easily; adapting to the environment and occasion as I see fit.

Well, we might not be able to do this with pants but now we can with Enterprise Applications. In fact, this type of flexibility, customization and efficiency of a solution that adapts to multiple needs will be the standard in five years time. Three forces are aligning to make this happen.

  • Web 2.0 – user empowerment and customization
  • Ajax – technology techniques to bring richness and back-end interactions to the user
  • Services – Exposed through SOA or other, services are the enterprise applications building block of tomorrow.

These forces are aligned to support the next generation of Enterprise Applications that will be common place in 5 years. These applications will be browser-based. They will unlock the value of information previously contained in separate silos through granular services. With AJAX client side technology, they will consume these assets and allow users to interact in a rich and dynamic fashion. And with the 2.0 social networking and collaboration aspect, the tilting of the IT pendulum back towards the client side leads to more empowered end users capable of generating content and even their own ad-hoc, mashup applications.

Now you can customize your organizations applications to your needs instead of forcing your employees to adjust to a heavyweight, monolithic solution that might not be a right fit for their need. Even further, you can empower your employees to further tailor the solution to meet a particular situational need when they need to.

Why will these applications be the standard?

This new paradigm is difficult for some to grasp. We have been offered large solutions that we had to make fit into our organization and make work for what we had to get done in our jobs. But the productivity that these applications brought to transactional activities is drying up. The future is focused on the knowledge worker who has tacit activities to accomplish and where no solution has arguably truly demonstrated much benefit with regards to optimizing these people’s situational activities.

This is where organizations can increase productivity. The problem is that because of economy of scale past applications couldn’t be developed to meet these situational, micro activities needs. The technologies weren’t all there, understood enough, or further, understood in the context of their synergistic relationships which yield the capabilities to meet these knowledge workers activities needs.

The Enterprise Web 2.0 Application can. It can because the forces listed above are now converging. Enterprise Web 2.0 is a natural evolution of consumer facing Web 2.0 Applications. Web 2.0 has introduced public consumer users to its benefits and now enterprises have begun to catch on to the technologies and techniques to further their web-based applications; to leverage existing assets, whether it be data locked behind a firewall or intellectual knowledge locked in your employees heads.

I can’t wait to see what unfolds this year! (pun intended)

Read More...

Thursday, January 25, 2007

Does SaaS really stand for 'SOA and Ajax as a Service'?

I know, SaaS stands for Software-asa-Service. But it seems there is a recent and fast moving resurgence (which some call SaaS 2.0) being driven by many forces all coming together. And if we’re accurate, the forces driving SaaS 2.0 are Ajax and SOA. I always thought of SaaS 1.0 as an ASP that represented hosted apps, not really services. And especially not multi-tenant apps. But, this is starting to change in a big way.

Much of the credit should go to Salesforce. Not only did Salesforce stick with its “No Software” value proposition throughout the so-called tough Web-years, the company also opened up its services so third-party applications could too be delivered over the Web. This of course is called SalesForce AppExchange. The corollary to AppExchange in the consumer space is Amazon.com. Some execs at Amazon may have the grand vision of running all Web commerce consumer transactions through their Web services, but I’ve heard them say that they expose (latest count is ten) their Web services because they think developers and companies would find them as useful as Amazon does. Pretty forward-thinking to me.

This is only the beginning. If you follow the Long Tail, Amazon and Salesforce.com should eventually generate far more income from third parties consuming their services than from their own customer-facing software. A while ago I blogged about this and called it the Composite Company. A Composite Company is one that has built its business completely on other companies’ services. The interesting part is that applications are built by consuming services from multiple companies, not just one. When I wrote this, the term “mashup” wasn’t widely known. But, it really does represent an enabling architectural style to let developers and users integrate data from the disparate services. This is the only way it will work and the only way it will scale. Can you imagine if IT had to pre-integrate all services from all companies? Not gonna happen. When made available as governed, secure and reliable (businesses need these), these SOA services – which are truly built for consumption – will create an innovation playground to drive new Web applications that were never imaginable before. But SOA is just middleware, it’s not the whole solution. It’s Ajax that provides the “face” or the last-mile that will enable true Web applications to provide these solutions.

This all will evolve into a new market called the SaaS Consumer market and will be driven by three types of companies:

  • SOA-only Software Providers - A new generation of ISVs that only provide services, but not UIs. Think SugarCRM and Salesforce as a set of SOA-only services.
  • SaaS Market Enablers - Companies that know how to host, manage and secure services for application consumption.
  • Composite Company - A new generation of ISVs that provide applications and composite apps that are completely built by consuming SOA-only Software Providers running on SaaS Market Enablers datacenters.

Get ready for this. Not only will this cause a dramatic shift in how we develop Web-based software, but it will create a whole new market of company opportunities.

Read More...

Thursday, January 18, 2007

It's All About the User, Stupid!

Let me make a less-than-bold statement: the most important part of software is the user. So why am I on this subject, you ask? Don't I sell 'Enterprise Web 2.0' software? That's Ajax, SOA, mashups, etc., right? Sure enough. But I sell software that supposed to empower users.

I've just finished reading a great blog ‘The Peoples Interface Awards' that drives this point home. It's a nice and concise recap of how important the ‘human interface design' is in how users perceive systems (and their IT department).

As a software provider in an industry that makes the web more interactive (and, presumably, more user-friendly), we see the results of bad and good web interfaces every day. Stealing a phrase from James Carville, we often make the statement that 'Its All About the User, Stupid'. In fact, it is such a popular topic in our industry that we've even held webcasts on it.

The issue with this issue is that it is 'soft and fuzzy', without many hard metrics for tangible, bottom-line ROI. Sure, we have examples. We've seen good improvements in customer conversion statistics for e-commerce applications were the ‘Web 1.0' interface was poorly built. But such stats from a vendor like JackBe could be viewed as biased (as we did the work). So it's great to see that this issue is being given some CIO-level attention.

Long live the user.

Read More...

Sunday, December 10, 2006

Time or Vogue?

If you got to choose which magazine cover you were featured on, what would it be? Time? Vogue? Fortune?

What got me started on this line of thinking? Well, JackBe made the cover of Infoworld last month in their article, 'Top Ajax tools deliver rich GUI goodness'. It's a recap of 4 Ajax vendors: Tibco, Backbase, Bindows and JackBe, of course. I think it makes a good beginner's primer on some of the issues you need to consider when selecting an enterprise ajax toolset.

The screenshot in the upper-right-hand corner of the cover is an Ajax-based dashboard JackBe built for a customer. You can get the entire article in PDF format here (it includes the magazine cover).

OK, so it's not Time or Vogue. But 'any press is good press'. (Any know who said that line? I can't seem to find the source.) And certainly the folks at Infoworld did a nice job of highlighting our 'good side'.

What magazine cover would I choose? Probably Rolling Stone. But only if Annie Leibovitz took the photo.

Read More...