The Audio Working Group has published a Working Draft of Web MIDI API. This specification defines an API supporting the MIDI protocol, enabling web applications to enumerate and select MIDI input and output devices on the client system and send and receive MIDI messages. It is intended to enable non-music MIDI applications as well as music ones, by providing low-level access to the MIDI devices available on the users’ systems. The Web MIDI API is not intended to describe music or controller inputs semantically; it is designed to expose the mechanics of MIDI input and output interfaces, and the practical aspects of sending and receiving MIDI messages, without identifying what those actions might mean semantically. The Web MIDI API is also expected to be used in conjunction with other APIs and elements of the web platform, notably the Web Audio API. This API is also intended to be familiar to users of MIDI APIs on other systems, such as Apple’s CoreMIDI and Microsoft’s Windows MIDI API. Learn more about the Rich Web Client Activity.

The Cascading Style Sheets (CSS) Working Group has published a Last Call Working Draft of CSS Writing Modes Level 3. This specification defines CSS support for various international writing modes, such as left-to-right (e.g. Latin or Indic), right-to-left (e.g. Hebrew or Arabic), bidirectional (e.g. mixed Latin and Arabic) and vertical (e.g. Asian scripts). CSS is a language for describing the rendering of structured documents (such as HTML and XML) on screen, on paper, in speech, etc. Comments are welcome through 24 December. Learn more about the Style Activity.

It’s done: our brand new Smashing Book, full of smart, time-saving tips for crafting fine websites. Neatly packed in a gorgeous hardcover, the book features practical front-end techniques from well-respected Web designers. 498 pages. Hardcover and eBook. Available today. Get the book now.

About The Book

The book isn’t concerned with trends or short-lived workarounds. It’s focused on the actual design process—the why of the decisions we make as we craft websites. With New Perspectives, we look into lessons learned from mid-size and large projects and explore new, uncharted territories in Web design: mainly front-end, but also back-end, responsive design, typography, psychology, customer support, and content strategy.

Smashing Book #4 is quite thick indeed. Large preview

Written by well-respected designers and developers, the book contains lots of actionable takeaways that will help you improve your workflow. Think of it as a reliable playbook for issues that keep following you in every project. No, this book won’t change your life forever, but it will challenge you to look differently at how you build websites today. Available as print and eBook.

Why This Book Is For You

This book is for you because you’ll discover plenty of valuable, time-saving techniques that will improve your workflow right away. You’ll learn how to:

1. Create a robust, scalable front-end,
2. Write maintainable, futureproof code,
3. Keep websites slim and fast,
4. Bake performance into the workflow,
5. Build lightweight responsive sites,
6. Fix mobile rendering issues,
7. Build adaptive, smart interfaces,
8. Apply obscure back-end techniques,
9. Design with better Web typography,
10. Establish and maintain a content strategy,
11. Minimize and optimize customer support,
12. Understand how people think and decide,
13. Sharpen a new idea and follow it through.

Not convinced yet? Alright. Let’s take a look at the table of contents.

Table of Contents

We invited respected designers and developers who have a story to tell and experiences to share. The chapters have also been reviewed by active members of the community such as Jonathan Snook, Inayaili de León, Tim Brown and Sean Coates—just to name a few. Feel free to download a free sample to look inside (PDF, ePUB, Kindle, 14.74 Mb).

AUTHOR	CHAPTER	DETAILS
Vitaly Friedman	Preface
Summary • The Web is dynamic and versatile—coding techniques aren’t black and white, and so our decisions always emerge from those shady gray areas. In the preface, Vitaly argues why Web design today requires new, pragmatic, open-minded approaches and why it’s so important to look at our craft from new, unconventional perspectives. Keywords • best practices • strategy • trends • perspectives.
Harry Roberts	Modern CSS Architecture and Front-End
Summary • With websites getting bigger, their dev teams growing larger, and their goals becoming more tightly defined and, I dare say, more important, we need to take another look at how we actually build them. It’s no longer practical to spend days and days thoroughly hand-crafting code; a much more rapid, powerful and pragmatic approach is needed. In this chapter we are going to take a whirlwind tour of a new approach to building more powerful front-ends for the Web today. Keywords • semantics • misconceptions • Object-Oriented CSS • code structure • file organization • CSS selectors • portability • naming conventions.
Nicholas C. Zakas	Writing Maintainable, Future-Friendly Code
Summary • Code is code no matter where you go, and code has a tendency to get messy as it gets large and old. Things start to break, you find it hard to figure out why bugs are occurring, and there are parts of the codebase that seem to be “magic”. On a large project with many developers, the problem is magnified. How can everyone work in the same codebase in such a way that making changes in the future are easy? That’s what this chapter seeks to answer. Keywords • code smell • conventions • code style • comments • architecture • SMACCS • documentation • design document.
Christian Heilmann	The Vanilla Web Diet
Summary • Maybe we should take a break in our drive to be cool and new and innovative the whole time, simply for the sake of being so, and check what we are doing — analyze our eating habits, so to say. I call this the Vanilla Web Diet, much like people have started to call using JavaScript without libraries vanilla JavaScript. Here are some ideas and thoughts you can bear in mind to help slim down an existing website or your next app. Keywords • legacy browsers • browser-specific code • jQuery • frameworks • consistency • conditional loading • lack of support is an opportunity.
Tim Kadlec	Culture of Performance
Summary • Websites are getting fatter and fatter at an alarming rate. The issue is not the competence of Web developers. The issue is also not just technological: a lot of smart optimizations are usually implemented to get the weight down. Instead, the issue is the lack of a well-established culture of performance—a total commitment to performance from the entire team that would drive and influence decisions during the project cycle. Given the incredibly important role performance plays in the user experience, this is a disastrous mistake to make. Keywords • performance • case studies • visualizing performance • performance budget • the 20% rule • testing • atomic design • perceived performance • optimistic interfaces • preloading content.
Mat Marquis	Robust, Responsible, Responsive Web Design
Summary • Responsive Web design is starting to get a reputation—and not the kind of reputation that it rightfully deserves. The most common death knell we’ve heard ringing out is that every page of a responsive site is fated to weigh in at a couple dozen megabytes and there isn’t a single thing that any of us can do about it. This trend is on us, and you don’t see any carpenters writing blog posts about how hammers are a failed methodology because of the times they dropped one on their feet. We can do better than blaming our tools for our mistakes. Keywords • Responsive Web design • presumptive enhancement • progressive enhancement • accessibility • Ajax-Include pattern • conditional loading • responsive images and video.
Addy Osmani	Finding and Fixing Mobile Web Rendering Issues
Summary • While network performance is important and JavaScript execution is usually quick, many find that rendering (painting pixels to the screen) is their bottleneck. This can be a challenge as mobile devices are underpowered when compared to our desktop systems. To hit 60fps, we sometimes need to go beyond JavaScript as the sole performance bottleneck for our pages and spend more time investigating paint and layout issues. This chapter explores some of the core causes of jank in sites and applications. Keywords • performance • 60fps • rendering jank • faster animations • hardware acceleration • diagnosing slow paint times • workflow • remote debugging.
Aaron Gustafson	Designing Adaptive Interfaces
Summary • Design, as a concept, is a tricky little beast. Design does not exist in a vacuum. Each step in the process of building an interface should add to the experience. In the end, independent users may have differing experiences of the interface, but no one is denied access to a good experience. To create truly exceptional designs, we must not only reduce the friction inherent in completing a task, but we should make it (dare I say it) fun! We must reconcile aesthetics with usability. Keywords • empathy • the layer cake • constraints • lazy loading • construction flows • JavaScript support • adaptive components • atomic design.
Paul Tero	Obscure Back-end Techniques and Terminal Secrets
Summary • You wake up one morning, look at the browser window, check the Widget 3000, click on a button and there’s nothing. What happened? Help! The Internet is gone! We’re going to cover a lot of ground in this chapter, from routers to servers, from error logs to PHP hacks. I’ll start with the worst case scenario and work inwards, exploring the infrastructure of the Internet and the make-up of a Web server, imparting lots of little tips and commands along the way, opening up a new perspective on how websites can stop working — and be fixed. Keywords • back-end techniques • networking • router • DNS • traceroute • servers • firewalls • Denial of Service • HTTP • administration • error management • PHP errors •.
Marko Dugonjić	The Next Steps For Web Typography
Summary • In this chapter, we’ll cover the big picture first — with not too frightening context models and a list of actors that participate in content creation and publishing — and continue with practical details, with plenty of code examples and tips. Among other things, we’ll cover typefaces and Web typography in general, organization and performance, typesetting and advanced CSS techniques. Keywords • universal typography • multifaceted model • structured content • responsive Web typography • font delivery and distribution • rendering engines • macrotypography • combining typefaces • type library • CSS organization • fonts as progressive enhancement • subsetting • Base64 encoding • white space hierarchy • modular scales • subhead styles • advanced CSS techniques.
Corey Vilhauer	The Two Faces of Content Strategy
Summary • There are two faces to content strategy: the people we’re targeting (our users), and the people who are doing the targeting (our editors). We’re responsible for making great websites. But we’re also responsible for making websites that are usable from the editor’s standpoint. We are the people who make the Web; we are also those responsible for helping those who sustain it. Keywords • editors • content workflow • content discovery • auditing • strategy • assigning roles • execution • governance • editorial triggers.
Rachel Andrew	Supporting Your Product
Summary • Providing a good customer experience is really important in support. The customer may make that initial contact feeling annoyed about your product. They have an issue, and it isn’t doing what they wanted it to. Your aim should be not only to solve their problem, but to leave them feeling more positive about your product than they would if they hadn’t had the issue that brought them into support in the first place. Keywords • support as a marketing tool • feature requests • core use case • difficult customers • the end client problem • pricing models • minimizing support • tools • no FAQs policy • support statistics • social media • future-friendly support.
Nishant Kothary	The Design of People
Summary • The goal of this chapter is to introduce you to the human being as the center of every success or failure in our lives. But not in that tired way we’re all guilty of where we commiserate and vent on Twitter. Or the way where we publish blog posts about the bureaucratic deadweights that are the true bottlenecks to innovation. Let’s resist the convenient cover of insanity. Let’s stop putting more lipstick on the pig, and instead explore why the pig is so darn ugly in the first place. That is, let’s talk about the root of the problem instead of the symptoms. Keywords • psychology • communication • design reviews • the Sally-Anne test • theory of mind • cognitive bias • illusions of mind • strategy.
Christopher Murphy	On Creative Spirit
Summary • So, how do you establish an idea generation culture? How do you open the proverbial floodgates and unleash an endless supply of new and original ideas? Is it possible to adopt strategies that allow us to reliably generate meaningful ideas, which we can then execute skillfully? I believe, by adopting a simple mental framework and embracing a core set of strategies, it is. Keywords • idea-generation techniques • priming the brain • digital toolbelt • sketchbooks • strategy • centralized office • café culture • the Lego office.

From left to right: Harry Roberts, Nicholas C. Zakas, Christian Heilmann, Tim Kadlec, Mat Marquis, Addy Osmani, Aaron Gustafson, Paul Tero, Marko Dugonjić, Corey Vilhauer, Rachel Andrew, Nishant Kothary and Christopher Murphy

Technical Details

• 498 pages, 16.5 × 24.0 cm (6.5 × 9.5 inches).
• A high-quality embossed cover with a little surprise,
• Quality hardcover with stitched binding and a ribbon page marker.
• The eBook version is included in the printed book for free (PDF, EPUB, Kindle).
• Airmail delivery from Germany ($5 worldwide shipping, check delivery times).
• Available as print and eBook.

If you’ve already ordered the book, then it’s really only a matter of days until you receive it. Until then, the complimentary eBook is waiting for you in your Smashing Shop dashboard. At this very moment, all orders are being shipped from Germany by airmail. Of course you get the eBook automatically once you’ve ordered the printed book, so you can start reading right away.

What Reviewers Say About The Book

Still not convinced? Well, a few reviewers had the chance to read the book beforehand, and share their feedback without any strings attached. Should you get it? Let’s see:

“Smashing Book 4 provides logical, practical, real-world examples of what’s wrong with modern sites and how to fix them. [..] I want the Web to win. But to do so, Web development has to match its age and live up to the responsibility it has earned. The book takes a big step in guiding that transition for both products and people, making it a book I would very strongly recommend for everyone involved in Web development.”

— Dudley Storey, Review: Smashing Book 4

“The Smashing Book 4 is excellent value for money. [...] [It's] conference quality topics in the palm of your hand, permanently committed to paper (or the medium of your choice) ready for you to consume whenever you want. The Web has grown up and The Smashing Book 4 is the perfect field guide for making and maintaining things for a future-friendly Web.”

— Jordan Moore, Review: Smashing Book 4

“Currently reading a preview of Smashing Book #4. Each chapter updates you on one important area of Web development and Web design which is really useful given the hectic pace seemingly every aspect of our industry is moving at. Nice to have it all distilled in one book.”

— Jamie Mason

“Just reading Smashing Book 4 and I can strongly recommend it. Full of practical and useful Web design stories.”

— Janko Jovanovic

Frequently Asked Questions

If you have any questions, we are right here to answer them. We love our customers, and we’d love to help you in any way or just listen to your story. So please feel free to ask questions via Twitter @smashingmag — we’ll get back to you right away. Just in case: here are answers to some frequently asked questions.

Thank You

Thank you so much for your support, everybody—we truly appreciate it. The book has been quite a journey for us, and it’s our privilege to share this journey with you. We hope you’ll love the book just as much as we do. We’re looking forward to your feedback. Ah, and have you solved the Smashing Book #4 Mystery Riddle yet?

© Vitaly Friedman for Smashing Magazine, 2013.

It’s a sad fact that the biggest problem freelancers face, is disagreements with a client once a project has started.

It seems — judging by the amount of problems overheard by complaining designers — is that terms, changes, direction, and payments more often than not become roadblocks to a smooth and successful working relationship, usually ending what could be a continuing relationship between the freelancer, and client.

There is a simple, logical, and professional way for both parties to understand each other with complete transparency. Unfortunately, it’s a step many creatives skip.

Where do most creatives stand on paperwork? 

According to a recent survey, 39% of designers don’t require clients to sign on the dotted (or any) line, to take on a project. It’s a fairly safe assumption that a formal creative brief is another form most creatives don’t use. 

The same survey reveals that creatives prefer clients who know what they’re looking for at the outset of their design project, and score points with designers. 51% of designers surveyed consider that one of the most important characteristics in a client. 

The opportunity to be creative, and design something cool motivates 62% of designers to take on a project, compared to 48% who are swayed by fat paychecks and just 6% who consider a client’s prominence key. 

48% of designers say the lack of helpful feedback is among their biggest challenges in working with clients, while 42% point to clients’ lack of direction, and 25% indicate unrealistic expectations as major obstacles. 

With all of this in mind, how can a designer, or design staff, achieve all of these, and protect their rights, and sanity? The answer is a creative brief.

Why a creative brief solves problems 

Ask someone to sign a contract, and they will usually have a reason as to why they don’t want to sign. A contract contains hard, and fast rules of the business end of a project. The length of execution, change fees, payments and rights of use are some of the elements spelled out in a contract. With careful wording, a creative brief can hold all of that information, too! 

When first sitting down in the office, or conference room of a client, or meeting of the different players in your company, it’s time to start taking notes on what is said, asking certain questions, and… setting requirements, and boundaries. 

At one firm, which was a very large corporation, we would all sit down in the conference room for a project meeting. Each department head would listen to the project scope, and desired results. Like a puzzle, each step depended on every department meeting the milestones set so the next department could pick up there, and supply the needed elements only they could provide, and so on around the company until it fell upon the art department.

If one department took too long with their part, like a tower with a missing part in the middle, the project would start to tumble down. Unfortunately, it would always be the art department that would be crushed under the weight of the steel beams of incompetence, supplied by other departments. 

The creative brief, written up, and sent out by the art department served to hold people responsible. In regular meetings during the project, it made it easier to ask other departments where they stood on their milestones, and why, inevitably, they were late. With a sympathetic, and strong project leader, responsibility, and meeting deadlines will make sure that creatives won’t have a week to create the final project when other departments were to take only two weeks out of a two-month project. 

It seems that at most companies this is the standard operating procedure. It’s rare that a project manager can or will keep tight reign on milestones. It’s even more rare that there’s a professional project manager at companies. Usually, someone will be assigned as a project manager, and they might not have enough experience, or the corporate level to demand strict adherence to milestones on a project. In a corporate setting, this usually leads to problems with getting a project done on time. In a freelance situation, your time is your money, and when you end up either working an extra week, or so on a flat fee, trying to charge for extra hours, or working an extreme rush to make a deadline, it’s a losing situation for you, and can lead to a project that probably won’t be your best work. In the end you’ll get the blame, and although unfair, well… welcome to business! 

So, how do you protect your reputation, income potential, and show yourself to be a valuable vendor to a client, or a competent project manager to your corporate boss? Start with a clear, and concise creative brief, and an iron fist! If written correctly, the information you include will leave no stone unturned and, no question unanswered. It’s not really hard. 

In the long run, a complete, and clear creative brief promotes transparency for all parties, and that is one of the things clients appreciate in a creative project, where they don’t fully understand the creative process.

How to get started 

The computer did not, as promised, make us a paperless society. Digital communications added to the lack of memory people have. Computers, in a big way, replaced our ability to remember, and store information in our own brains. An example is when a client doesn’t remember you saying something on an email, like asking to be paid, or trying to find out why the three-day period for a decision on final designs has taken 17 months.

Organization is the key. When I first started my design career, working both freelance, and on staff, I would create a job folder for each, and every assignment, and project. I started by labeling the folder, and then having a short creative brief written on the outside of the folder. It listed the following: 

• Name of the project.
• Date I received it.
• Date the project was due.
• Who was involved in the project, their names, phone numbers/extensions, email addresses.
• Milestones for materials needed from these people.
• From there, as the project proceeded, I would write down notes of what was happening on a daily basis.
• Were we on time?
• Were there requested changes, and by whom?
• What milestones were missed, and by whom?
• When files were delivered, and to whom. 

Within these file folders, I placed all printouts of the design stages, emails from other departments/people, and anything else that pertained to the project. Most of my bosses commended me for “knowing where the project was at any time.” 

At one employer, where incompetence was encouraged through rampant Peter Principle, I was told my file folders, “made people nervous.” 

Of course people were nervous; it held people accountable. It’s not that the folders were set up to embarrass people… well, I admit that it was a part of it because the blame-game was big at that firm, and I had to protect myself from the lying finger-pointers, which really infuriated them to no end, but it was also the only way to keep a 100% on time delivery record. 

The plain fact is that these folders were invaluable to juggle what was sometimes two-dozen projects going on at once. Multitasking is nothing more than being organized, and there are tools one can use for that organization. The “Folders of Evidence, and Blame,” as my boss referred to them, were invaluable. 

While these were somewhat private creative briefs for myself, it’s best, when managing a project, especially on a freelance basis, to have a written brief for everyone to retain for their own folders, if they have one.

Creating a brief 

I’ve looked at other creative briefs available on the web and frankly; I’m not impressed with what I saw. The examples available didn’t cover enough to really let the client know all of the steps nor did it cover the creative’s end of the project. Here’s a brief that you can use as a template for your next project:

Client/Client contact information:

Name, phone number, and email address for the person or the team on the client side.

Project:

Title of project

Prepared by:

Name, phone number and email address for the person who is responsible for in-house project management.

Background/Overview:

Detailed description of EVERYTHING that needs to be done! Include absolutely everything you can think of that will be included so any scope creep can be billed separately.

Timeline/Milestones:

Start time: Date goes here.

Client delivers images/logos for brochure, web banner, and web site. All proofread copy delivered by client. 

1st Milestone:

Sketches for design of all components – (set date).

Client revisions/approval by (set date).

Revised sketches delivered by (set date).

Client revisions/approval by (set date).

*Further revisions will change milestones. Adjusted brief will be resubmitted to client. 

2nd Milestone:

Second stage design – (set date).

Client revisions/approval by (set date).

Revised images delivered by (set date).

*Further revisions will change milestones. Adjusted brief will be resubmitted to client. 

3rd Milestone:

(Set date)

Presentation of completed designs to client for viewing/approval.

*Further revisions will change milestones. Adjusted brief will be resubmitted to client.

4th Milestone:

(Set date)

Uploading, or delivery to printer (set date).

Payments:

Fee: $ (total fee for project)

Deposit: $ (set fee – should be one-third to half of total fee). Deposit due at start time.

1st Milestone: $ (percentage of total fee)

2nd Milestone: $ (percentage of total fee)

3rd Milestone: $ (percentage of total fee)

4th Milestone: $ (*ideally, this should be the final percentage of the entire fee for the project)

* Changes beyond the first round (further changes) will be billed separately at a rate of $ (set hourly rate) per hour.

Rights:

Client purchases all rights to design/copyright for work rendered. Transfer of copyright is contingent upon full payment.

This, of course, is just the basics as an example. The more you list, going into the smallest details, the more you will protect yourself against “misunderstandings” as the project proceeds. The biggest problem with any project is the “but I said…” or “I thought this would be…” and the ever popular, “I thought we were going to add this?”

While a contract spells out rights, payments, and promises kept only through legal wording, a creative brief shows all parties how the project will proceed, and, most importantly, how payments will be made. With a contract, people may see it at the beginning of the project, but won’t look at it again until you are threatening to sue them for breaking your agreement. The creative brief reminds people every step of the way that you won’t work for free, excessive changes will cost more.

Still, a creative brief may need to include the demographics of the customer/target audience. Although I haven’t experienced it myself, I have heard from other designers about clients who set the design standards of a project, but later complain that the work doesn’t reflect their consumer base.

Make the language clear

One example I can relate about a language misunderstanding was a company president who kept using the word, “sophisticated” for a design project. With every design sketch, she would say, “No, no, no! I want sophisticated!”

After eleven attempts at “sophisticated,” I finally asked her to show me some examples of what she liked, and I would take it as inspiration. After she pointed out a few examples, I realized she was wrong, and severely nuts! What she really wanted was something whimsical. This is a great, and painful, example of miscommunication, and how much work just one word — one descriptor can cause. I was on staff at the company so it wasn’t as big of a deal as if it was a freelance assignment, which would have been a disaster if it were a flat fee. It was just an extreme waste of time, and a tick that showed up on my annual performance review as, “failed to satisfy the president’s wishes in eleven rounds of changes.”

This is yet something else that needs to be included in the creative brief. Words can be misinterpreted, or misused. Sometimes people use their hands to describe what they want, moving them up, and down, and sideways to specify size, layout, or “sophistication.” Your job, as the creative lead, is to pull out from the odd babbling what it is they really mean, and place it into the written brief so there are no extra rounds of design that cut into your fee, or take you away from other projects.

Demographics are another important point to clarify for the creative brief. Who is the intended audience? The answer might be “everybody,” and it might be “18-28 year-old men who live in their parent’s basement.”

Remember to ask these questions so when you are ready to write up your brief to present to the client, there will be no holes that might trip up the project down the road. If there are any holes, or misunderstandings, the time… and money, will come out of your end, and that can add up over a year to thousands of dollars.

When trouble arises

Anyone who tells you they have never had a problem with a design project is either a liar, or a psychotic. There are projects that run up against certain questions either during, or after a project is complete. Usually it’s getting paid when a client questions how much work has actually been done, and why the project costs more then $79.

Seriously, we laugh at that statement but we all know it to be true. In cases where you must sit down with the client, and go over all aspects of the project, and show proof of requests, changes, and costs incurred by you, the folder will hold all of the answers. Naturally, the client might not agree that the answer they sent in an email, telling you that all designs are approved is really what they meant, but that leads to another avenue — court.

If you are forced to go to court or mediation, the project folder is a legal dream — maybe an orgasm! Everything in writing, in one place and ready to present as the record of each step. Even if you have no contract (you should have one!), the project folder, and the creative brief will show intent, agreement, and steps taken to complete the project.

You will also find that creative briefs are handy for repeat clients. In web design, it’s important to retain clients to service their ever-changing web needs. As technology evolves, and companies grow, the original creative brief serves to remind you of how the client prefers to work with you. Reviewing past project files, and briefs can also remind you when it’s time to contact a client to pitch updates to their site. It’s a wonderful tool that’s valuable to your business. So, run out to your local office supply store, buy some file folders, design a creative brief sheet with your logo on it, and you’ll see how easy a great creative brief, and project folder can make your life and business.

Do you use a creative brief? Has it helped your projects? Let us know your experiences in the comments.

Images ©GL Stock Images

Imgimage: Choose Among 2 Million Stock Images – from $15!

API’s are essential to the development of an interactive webpage, they play a major role in the World Wide Web today, this article discusses the necessary points of an API to which any respectable developer should understand and be familiar with.

ConnectWise’s new SDK serves as a one stop shop for all APIs so developers don’t need multiple service references to the source code.

MyEclipse Bling is a specialized IDE allowing IBM shops to fully and completely adopt Spring technologies in their WebSphere-deployed applications from start to finish.