What Developers Want

If you are a Development Manager here are 5 things that your Developers will thank you for.

1. Quiet: Developers want and need quiet uninterrupted time to write code and solve problems. The need for continuous hours of quiet, uninterrupted code writing is crucial. Uninterrupted means absolutely uninterrupted. Do all you can to restrict direct access to Developers.

For the definitive answer on quiet, and why it is a Developer priority, see Paul Graham’s post: Maker’s Schedule, Manager’s Schedule.

2. GSD: Cut the non essentials and Get Stuff Done: Read Getting Real, by Jason Fried and David Heinemeier Hansson (37 Signals, now Basecamp).

3. Trust: One good Developer will accomplish more than 10 average Developers. Find your top-10 Developer(s). Trust him/her to guide you in the right direction. Don’t manage developers by committee or consensus.

4. Flexibility: Developers are unique individuals. Developers will get more done working at home than when working in the office. They will thank you if you can solve simple life problems, like suggesting work at home while waiting on a delivery. Learn the unique ways to reward each developer.

5. Professionalism: There are 2 types of Developers: (Type B) those that go home after 8 hours and (Type A); those that code at home for fun, read about development, go to meet-ups and conferences, teach others, and contribute code to the open-source community. Promote and protect your Type A professionals.

One last idea for the non-Developer Development Manager. Learn how to code and learn the language that your Developers speak. If you take this as a homework assignment to do on your own time, you will better empathize with the Developer who is working after hours or the one on call for production code.

“One really good person will get done in a day what ten not-so-good people will never get done.”
~James M. Spitze, SCC Sequoia

On-boarding – Key to a Great First Impression

You really can’t overemphasize that first day at work experience. When I arrived at my first professional job, my new manger eventually came to meet me. The next words as we walked on were: “now, where am I going to put you”. I realized that he hadn’t thought about me after the interview and had done nothing in anticipation of my arrival. I definitely didn’t feel welcomed or that I was part of a team. I’ve never forgotten that first impression.

As a hiring manager you can make sure a new team member is expected and welcomed. After all, they have just gone through a grueling job search process and chose you over another job somewhere else. Have a clean desk with all the equipment they will need and introduce them to everyone, even if they previously interviewed with everyone. Have an on-boarding agenda that lets the new person spend time with each team member and start them immediately on a first project. Arrange for lunch on the first day and make sure they find their way around. Introduce them outside of the immediate team and with other people whom they will work with. Consider an after-hours team meetup with the new person before their actual start date. Do all of this is in addition to HR’s on-boarding process.

“Life is not a dress rehearsal.”
~Rose Tremain

The Power of the Monthly Report

The Monthly Report is a lost art. We may have been too quick to abandon this artifact or, possibly, it was never a part of your company culture or personal habit.

Consider the positive returns gained from a small investment of time in creating a monthly report. As a checklist-driven person I see obvious benefits of documenting where you’ve been, even if you are the sole reader of your very own monthly report.

Benefits:
A monthly report is a report card to yourself, your management or to your company. After all, if you believe in what you are doing and that you are doing a good job at it, why wouldn’t you want to share that? By periodically looking back you can track your progress and trajectory. Are you heading in the right direction? Are you meeting goals, deadlines, and any required administrative check-offs?

People love recognition. If you can recognize the achievements of others it has a powerful effect on future performance. Recognition, especially in writing, is an awesome productivity tool in itself. The Monthly Report is a great place to regularly share team successes.

A summary of monthly reports automatically yields quarterly and annual reports. Collectively these reports are irrefutable personal leverage at performance review meetings.

And – possibly most important – monthly reports are key to updating your resume.

Format:
Keep the report format simple. A monthly report can be as simple as a list of dated entries in a journal. If the report is to be shared/upward you might establish a consistent format, with meaningful metrics and results. If monthly reporting is too frequent, consider keeping notes and creating a summary every few months.

“I’m trying to free your mind but I can only show you the door.”
~Morpheus, The Matrix

Website Activation

Where’s Waldo? How to activate a website with a contest!

I’d like to share a technique once used to activate a new website and get 100% of existing clients to happily switch over to a completely new version of the website.

  1. First we launched the new website and kept the old site running.
  2. Next we promoted the new website from the old one using a “Where’s Waldo?” contest.
  3. If you found an image of Waldo on the new site you could enter a drawing for prizes.
  4. Every day we would give hints about where to find Waldo – and over a period of time directed everyone to the major areas of the new website.
  5. Once a week we would announce the latest contest winners, which would bring more clients over to the new site.
  6. After users found their way around the new site, they didn’t bother to go back to the old one.
  7. We also discovered that our particular client base loved contests and awards.

I can’t take credit for this idea. My friend (and he paid me to add this: creative genius, wine connoisseur, dog lover, philanthropist, master of irony and all around trend-setter) David Pearson came up with this idea that we used for a large insurance agency portal implementation in 2004. In 2005, the website was awarded recognition by A.M. Best as the top Insurance Agency Portal website in the U.S. Our Where’s Waldo website launch technique was part of the presentation leading to the award.

“Sales reps are coin operated.”
~Mark Vayda

Maintaining Technical Currency

It’s essential to stay current in your career, especially if it centers on technology. The #1 way to stay up-to-date is to become and remain a practitioner – learn by actually working with specific technologies “hands on”. Second – continuously track state-of-the-art changes. And third – expose yourself to as much information as possible about specific technologies, related businesses, and information from people who are driving change in technology.

Here are some ideas and resources to consider in maintaining technical currency: Continue reading

Whose Generation

Every generation is labeled. Each generation is a product of their culture, disciplines, education and shared experiences, just like every generation before. The current generation always gets a bad rap. Let’s not condemn it if we don’t seek to understand it. Here are some of the comments I’m hearing:

  • Time has more consideration than money
  • Some are uncertain of the American work-ethic after parent’s corporate experience
  • Instant communication is a given – so are instant decisions
  • Email is one of the slowest forms of communication
  • An abundance of knowledge and entertainment, 24 x 7
  • The current generation actually do multitask
  • Typing is learned along the way – not a class you take
  • Being digital is just normal
  • Most processes are born digital – not automated after-the-fact
  • Some question the corporate employment model; 1 in 3 U.S. workers now freelance (2014 stat)
  • Work -> Save -> Retire is no longer an option
  • Quality of life has value over quantity of stuff

“Being rich is not about having a lot of money, being rich is about having lots of options.”
~Chris Rock

Ground Hog’s Day 2.0

The hallmark of a true professional is the ability to treat each person and situation with the same enthusiasm and interest as you did the very first time. This means that you will repeat yourself any number of times on the same or similar topics with the same or new clients. This is especially difficult for developers, who are trained to get to end point as efficiently as possible and, specifically, don’t repeat yourself (DRY principle).

I’ve recently put myself in someone else’s shoes – practicing patience and empathy. All I asked was that they do their job at the same quality level that I do my job. Is that too much to ask? It may in fact be too much to ask if the other person is put into an untenable situation, with no support from the company they represent. Imagine if you lacked the wherewithal to make a difference and had no control over your time or schedule and did not have the tools and resources to get things done. This person is responsible for delivery and installation of expensive equipment. However, the very company that stands to lose from a bad customer experience almost guarantees failure upon final delivery. Why so much emphasis on selling instead of delivery and service?

If you don’t support your team all the way to delivery of the end product you may in fact have a broken process. What kind of feedback loop do you have in place to find out what the customer experience is really like? I highly recommend that you follow your service or product to the end delivery point to see the results from your customers perspective. If you use 3rd-party sales, delivery or service reps then it is even more important to monitor final delivery results and follow up after the sale and delivery. A “Voice of the Customer” survey is not nearly enough to ensure customer satisfaction and good word-of-mouth referrals.

Repeating a broken process on a daily basis will not eventually fix the process.

“Success consists of going from failure to failure without loss of enthusiasm.”
~Sir Winston Churchill

Breaking Development Conference
Nashville July 2014

Breaking Development Conference – Nashville – July 2014  #BDCONF
Gaylord Opryland Hotel and Convention Center Nashville TN, July 29-30, 2014

THE VENUE
The Opryland Hotel and Convention Center is an immense hotel and conference center, with 40 acres of shops, gardens, and restaurants under roof. The hotel boasts 2,884 rooms. It’s fun just to find your way around the hotel and an awesome place for a web development conference. Over 152 meeting rooms; 600,000 sq. ft. of total meeting space. One ballroom alone has capacity for 7,050 people.

CONFERENCE FORMAT
I really like the format of Breaking Development conferences: Best-of-class speakers, top sponsors, and all sessions in one room, one at a time, with everyone hearing the same thing at the same time.

Attendance is limited and not crowded. I estimate 175 were in attendance, plus speakers and the terrific conference folks from Unmatched Style. You didn’t have to scramble from one track and session to another and don’t miss one session in favor of another. Great way to run a conference, with plenty of time to meet with both other attendees and speakers.

#BDCONF used MailChimp’s Gather App to send txt updates to attendees throughout the conference. This was a great way to keep everyone in synch, especially about evening meetups, etc.

CONFERENCE TAKEAWAYS
Emphasis was on mobile design and UX. I saw 2 main themes: (1) the state of mobile web and how we are struggling to move our design mindset from large screen to small, and (2) new approaches to managing web design/development projects and getting to done (#GTD) faster.

~~~  ~~~  ~~~  ~~~  ~~~   ~-~  ~~~  ~~~  ~~~  ~~~  ~~~  

Following are links to individual session notes from Breaking Development Nashville July 2014:

If you missed the conference in July, the next Breaking Development Conference is in Orlando November 3-5, 2014

Other Takeaways from Breaking Development Nashville – July 2014:

  • Expectations of device: location, context, voice, …
  • Lotsa bashing of the Hamburger Menu. It’s only intuitive to designers/developers.
  • Don’t use Carousels. They don’t convert to click-throughs.
  • Tip: Collaborate on a Google Doc to share note taking.

“If you want to go quickly, go alone. If you want to go far, go together.”
~African Proverb

Small Screen Navigation – Ben Callahan

Breaking Development Conference – Nashville – July 2014
Conference Session: Small Screen Navigation
Ben Callahan – SparkBox

A review of current mobile design patterns for navigation and interaction. Trigger Indicators and Interaction Patterns.

My Notes:

  • Don’t assume the big companies got it right. Don’t blindly copy patterns.
  • Vast differences in nav indicators and response across sites (e.g. “>” on some sites opens/closes a menu; on other sites it takes you to a page).
  • Content First – make sure we are building the right nav.
  • Give priority to high use cases.
  • Focus – overlay content with nav, e.g. content half hidden while overlay with menu.
  • Behavior – e.g. single top-to-bottom accordion menu JavaScript – strive for a single DOM.
  • Fallbacks aren’t worth it. Start with the lowest common denominator.
  • Usability – Web Designers understand Hamburger Menu, average user does not.
  • “Familiarity breeds usability” e.g. same nav on PC and Mobile.
  • “Design without testing is guesswork.”

Other conference notes on Ben Callahan at BDCONF can be found at: Ben Callahan notes on Speaker Deck

“You cannot do timeless work on your own. It takes a team. Collaborate!”
~Ben Callahan

Real World Responsive Web Redesign – Jonathan Stark

Breaking Development Conference – Nashville – July 2014
Conference Session: Real World Responsive Web Redesign
Jonathan Stark

This session discussed the RWD/redesign of Entertainment Weekly. I took away more about about project management than RWD but I was more so looking for PM tips.

My Notes:

  • RWD Guiding Principles: speed is a feature; progressive enhancement from low device to high; assume low; easier to progressively add features than to degrade gracefully.
  • Design: No Big Reveal – Constant feedback during design. Final design is 1 week from last review.
  • Big Pieces From Client: we knew all photos, videos, etc. from current site, and challenges before we started design process.
  • Advertising is a big challenge for mobile.
  • Prioritize Design with typical sticky note voting. Allow 20 seconds for +/- reactions to similar sites or comps/mood boards.
  • Set Initial design decisions: e.g. no carousels, progressive content, etc. Now you have a roadmap.
  • Did not use Agile or Waterfall but a hybrid, with information architecture, visual, and development in parallel.
  • Weekly build and push to dev site. Weekly all hands review with client. Weekly freeze.
  • Throw out elements client doesn’t like (e.g. which callout do you not like). Thereby weekly not a sign off.
  • Always design and demo in the browser, not comps.
  • Emphasize phone view in weeklies.
  • Start with small scale elements for review (e.g. and build to footer, then pages).
  • JavaScript: “Every script has a cost”
  • Consider starting with a site that works without JavaScript.
  • Create your own JavaScript library is better for minimum footprint. Don’t go to extremes with JavaScript.
  • Help yourself out: Use a common/single bug tracker; lots of screen shots for bug documentation with re-creating; we used multiple trackers – should have learned GIT better; automate deployment.

“Communication Trumps Process!”
~Jonathan Stark

Content First UX
Steph Hay

Breaking Development Conference – Nashville – July 2014
Conference Session: Content First UX
Steph Hay

Steph Hay presented a fresh approach to web site design by way of defining all of the content and information architecture up front, before you make the first wireframe or comp. The result is an outline of the site’s IA, which resembles a sitemap but is a complete definition of the site and actual copy. This reverses the typical process of adding content after design.

The process follows a user journey/dialog that is approached as a conversation. Elements of gamification are used to help the user seek goals and reinforce the learning experience along the way. Hay spent time in her presentation on this aspect of the process, which I cannot do justice here – but it’s important to the process. My main takeaway is her rethinking of the site development process. Putting content first makes absolute sense if we believe that content is the foundation of website experience.

My Notes:

  • Content First: Create the content and information architecture first, without tradition wireframes and other design techniques. This is a design-agnostic methodology.
  • Feels like a conversation. Promote user engagement.
  • Write all the content and structure in an outline [yields sitemap byproduct].
  • Greatly speeds up the overall a development process by improving front-end definition time.
  • Note: more than one speaker stated a ratio of ~3-to-2 | definition-to-build/activate.
  • Content First is inherently low risk, low res, and low cost. Promotes greater collaboration and helps define the end result more quickly without getting bogged down in design (speculative) considerations. Will result in faster overall development and launch.
  • Use with analytics to determine audience and solve the right problem.
  • Make a content workbook.
  • Language Boards: Core messaging; Choose Your Own Adventure style.
  • Ben &Jerry’s content written from a single statement/tag line.
  • User is Hero; Iterate until you win.
  • Conversation rather than structure. Hero journey; next steps…

Book reference: Make It Stick: The Science of Successful Learning (not Made to Stick) – some degree of difficulty in learning improves retention; applies to user journey as well.

Other conference notes on Steph Hay at BDCONF can be found at: http://www.lukew.com/ff/entry.asp?1899

Steph Hay on YouTube | How Two Startups Used a Google Doc to Plan Their User Interface

“Content Defines Structure, not the other way around.”
~Steph Hay

Mobile Design Now
Luke Wroblewski

Breaking Development Conference – Nashville – July 2014
Conference Session: Mobile Design Now
Luke Wroblewski

Luke Wroblewski is synonymous with Mobile First. He set the mobile design tone for the 2-day Breaking Development Conference.

My Notes:

  • Lots to learn but more to unlearn about mobile.
  • Above the fold: Scrolling is a continuation. Clicking is a decision.
  • We’re trying to fit large screen to small.
  • Hamburger Menu is a case of follow the leader imitation. The word menu, outlined to appear as a clickable object, was interpreted as a menu 21%+ more than the Hamburger Menu in A-B testing.
  • It takes big changes to go small.
  • Compared hotel sites with +/- 50% difference in process steps. [the difficulty of any extra field or step is magnified in mobile]
  • Startup: Release/Refine/Repeat; Learn Faster

Luke Wroblewski conference notes can be found at: http://www.lukew.com/ff/

[On Mobile] “It takes big changes to go small.”
~Luke Wroblewski

5-Day Rapid Prototyping
Daniel Burka – Google Ventures

Breaking Development Conference – Nashville – July 2014
Conference Session: 5-Day Rapid Prototyping and Testing – Build for Speed
Daniel Burka – Google Ventures

I’m not sure which Breaking Development session was my favorite but I could really relate to the information about rapid prototyping presented by Daniel Burka of Google Ventures. I was first introduced to rapid prototyping in 1986. The concept is the same today but we have now learned to include the client and customers directly in developing the solution in order to be successful. Amen.

This was an excellent session on rapid prototyping and, more importantly, about quickly getting to a high quality decision on the viability of an idea. Daniel Burka is with Google Ventures, the VC arm of Google. He has prior history with Digg and Milk, both of which are startups by Kevin Rose. Rose is a General Partner of Google Ventures.

A 5-day Rapid Prototype sprint can be applied to many different business ideas, technical or not. The presentation at #BDConf was based upon applying the process toward improving overall sales at Blue Bottle Coffee, based in San Francisco.

5-day Rapid Prototype:

Day-1: Put pressure on the team up front. On Monday, invite 5 prospective/customers to evaluate the prototype on Friday. Five is enough to provide an adequate evaluation and to complete the eval in one day.

Analyze: Dig into the design problem through research, client interviews, and strategy exercises. The client also participates. Listen and learn. The team includes both client and Google Venture folks. Build user flows, look for patterns and thoroughly understand the problems, constraints, and goals.

Day 2: Start to design solutions – but don’t group-think or brainstorm. Rapidly develop as many solutions as possible. Create multiple, individual solutions. By end of day two you want 10 to 20 divergent solutions. Actually write the copy, make sketches that can be matched to real images for build, and sketch out and document each idea thoroughly so that it can be directly prototyped.

Day 3: Select from among the ideas, as whole solutions or an amalgam of ideas. This is not a democratic process. Everyone votes with blue dots on mock-up sketches. All ideas compete and are pitted against others in a bake-off. Executives and leaders who are most responsible get extra/super-votes (e.g. red dots). Being democratic will water down the ideas, just like brainstorming creates design-by-committee solutions. By end of day three you want your three best options.

Day 4: Build the Prototype, usually as a website and/or mobile site mockup: Burkas demo of a low fidelity prototype was actually very graphically rich. Keynote or Power Point make good prototyping options (Keynotopia). Make the prototype clickable, with design elements to simulate real web pages. Use a technique that also makes the demo viewable on a smartphone, tablet and laptop PC.

Day 5: Validate: Show the prototype to the people you invited on Monday to learn what works and what doesn’t work. Again, keep it simple. Burka talked about using a USB camera to view and record phone interaction, over-the shoulder of the customer/test client. No 2-way mirrors and lab coats.

~~~  ~~~  ~~~  ~~~  ~~~  ~~~  ~~~  ~~~  ~~~  ~~~  ~~~  ~~~  

You may also want to read about Google Ventures’ Rapid Prototyping process as documented by Google Ventures and at Venture Beat:

The Product Design Sprint, 5-day Recipe for Startups (Google Ventures Methodology)
Jake Knapp – Design Partner Google Ventures

How Google Ventures Does Rapid Prototyping ‘Design Sprints’ With its 170 Startups

Here’s a link to a video of the presentation: Video: 5-Day Rapid Prototyping – Google Ventures

“We can’t solve problems by using the same kind of thinking we used when we created them.”
~Albert Einstein

Build Platforms, not Solutions

I say this quite often but have never written about it: Build Platforms, not Solutions.

It became clear to me when I was in that middle-stage of project/developer evolution that it was much more efficient to build a platform than a one-off solution. It’s way better than the idea of custom developing new solutions for every problem that you deal with.

The idea of platforms really hit home on a project where I had developed an expert system and needed a way to get information out of the system. My “solution” was to create an object-oriented, tree-walking method that would extract only certain objects …blah, blah, blah… And then an engineer said to me: “Oh – why don’t you create a report writer!”. Always in plain site but invisible to me, that suggestion opened my eyes.

The idea is to extrapolate the problem to the next higher level and create a more universal tool to solve the immediate problem as well as similar problems. Better yet, make that a part of a whole bunch of common solutions in the form of a platform.

It’s always easiest to solve the problem at hand with the quickest and surest solution. If you take the time to look at the problems that you are solving you will likely find a number of separate solutions that, taken together, will comprise a platform for a wide range of applications.

“Build Platforms, not Solutions.”
~Bob Reid

Startup Checklist

There is a lot information available about how to setup and run a small business. Here are a few resource links that float to the top. These are aimed at setting up shop from an operational perspective.

The following list provides money-saving ideas and resources for operating a small business or website startup. Please feel free to suggest ideas that have worked for you in the comments section.

Print: Vistaprint.com
Free Phone Number: Google Voice
Email: Google Gmail
Hosting: Winhost.com, Arvixe.com, too many to list…
Blog: WordPress, Blogger
Productivity: DropBox
Communication: iStockPhoto
Self-ed: W3Schools
Social: LinkedIn
SEO: Google Web Analytics
SEO: SEOMoz.org
SEO: SearchengineLand.com
SEO: Google Webmaster Tools
Productivity: EverNote
Communication: SlideShare
Shameless self-Promotion: SortFolio
Productivity: Dragon Naturally Speaking
Tech: Amazon Web Services (AWS)
Tech: Amazon S3 Cloud Storage
Productivity: SalesForce.com
Productivity: Google Docs
PDF Printer: PrimoPDF Continue reading

Promoting Projects to Success

The first step in a successful project, other than how it supports strategy, is to sell the project throughout your organization – up front and often. Once it’s fully supported and underway you’ll want to continuously promote progress and keep the team inspired.

Here are a few ideas to create awareness of your project and keep momentum.

  1. Get on the agenda of departmental meetings and talk up your project.
  2. Give the project an unfamiliar or catchy name that piques curiosity.
  3. Put a large project chart somewhere visible, near the team, and mark it up to show progress.
  4. Have team offsite meetings where you can focus only on the project (phones off!).
  5. Create a project logo.
  6. Get items printed with the Project Logo – like coffee mugs or tee shirts.
  7. Have a Project Launch! – but not too soon – and only one.
  8. Get logo stickers printed for the team’s laptops.
  9. Make 4 Dummies book covers and use for in-progress team awards.
  10. Celebrate early failures as learning experiences. Don’t be punitive.
  11. Use any excuse for food and beverages – often.
  12. Make progress updates in a company newsletter or blog. Start a project blog.
  13. Speak about the project at a conference (great for recruiting, too).
  14. Promote the fact that team members got some time off after the project crunch. Then – everyone will want to join your next project.

If you promote your project enough and recognize your team’s contributions you will have a line of people wanting to join your team.

Please let me know what ideas have worked for you for promoting projects and getting the best people on your team. Thanks!

“Focus on appreciation as much as achievement.”
~Tim Ferriss

 

Outsourcing Innovation

Does your workplace encourage innovation? While you might rightly answer yes, you may unknowingly use practices that discourage opportunities for innovation. This post is about common practices that, while effective, may actually remove the best opportunities for new ideas. Continue reading

Ask, Don’t Tell

Another interesting “active listening” technique that I’ve learned by observation is: reframing a statement as a question. in other words, Ask, Don’t Tell. For example: if you “ask” someone when something should be completed, instead of “telling” them when it’s due, you will get a much more thoughtful/active response. You also don’t take ownership away from the other person. (You do want them to take ownership and not come to you with every problem or question, right?) Continue reading

WAIT – Why am I Talking

I learned a new acronym last year that may help me become a better listener and better interviewer. WAIT means “Why am I Talking”. In other words, ask yourself if you should be listening instead of talking. It’s an important part of our jobs as web design, developers, and managers (or any job really) to deliver a solution that both meets the client’s needs and our own self-expectations. We can’t interpret our client’s needs if we don’t listen, repeat what we heard, and narrow the scope down to the essential parts crucial to success. Continue reading

Assumed Strategy

Everything that I consider about web design and development comes with the assumption that you are operating from a well defined strategy. Whether you’re a freelancer or corporate web manager – if you don’t have a strategy, you’re just building web pages.
Continue reading

The Universal Power of Tablet PCs

While researching mobile strategy I came to realize the universal power of Tablet PCs. No other device can access both old and new web sites and run apps, with a screen size that accommodates complex interactions. Smartphones provide all the same access but fail when a larger screen is really needed. In the form-factor tug-of-war the Tablet PC fits all of your needs except the “fits in your pocket test”.

The Tablet PC

  • Can view both mobile and web properties: websites, mobile websites, and apps.
  • Has a screen large enough for complex, multi-page transactions.
  • Can have both Wi-Fi and cellular connectivity.
  • Has a modern browser that can take advantage of responsive designed web sites.
Tablet PCs Span both Mobile Web and Apps

Tablet PCs have the widest range of mobile and traditional web access.

 

Decision Criteria for Mobile Development

Companies founded in the mobile age have an advantage. They’ve incorporated mobile from the start. Many companies are now working to incorporate mobile access into web applications and overall business strategy. Mobile can be a difference-maker and a budget-breaker. This post looks at two currently popular techniques to incorporate mobile access into websites and e-commerce: Responsive Web Design and Mobile App Development. Continue reading

Bloomberg TV Interviews Expedia CEO – Mobile Bookings at 20%

Interesting interview on Bloomberg TV with Expedia CEO, Dara Khosrowshahi. Mobile now over 20% of Expedia bookings. Mobile buy is “very much last-minute”/at point-of-need pattern. Expedia runs a multi-platform operation using responsive design techniques to adapt to PC/Tablet/Smart-Phone, requiring more “investment and design work” to achieve. iOS is dominant for Expedia mobile access in US; Android dominant in Europe and gaining in US. An Expedia app is available for both Android and iOS. Expedia App.
[6:30] Bloomberg TV Interview

Embedded Fonts – How To

By using CSS, it’s possible to use a non-standard web font on your website. Your web pages can reference 3rd-party fonts from a website, such as Google Fonts or you can install a font on your own web server and reference it from there. This post describes how to incorporate a new font onto a web server and make it viewable in the client web browser.
Continue reading