Close X

Kambi’s sportsbook is really nice, but why is it built in Flash?

Kambi, a B2B supplier of sports betting products, has developed a really good sportsbook product used by large igaming companies like and

Image 1. The Paf website using Kambi’s sportsbook product.

The sportbook design is really clean and I especially like the feature with the visible betting slip. The betslip is visible even when you scroll up and down the page.

Image 2. The betslip is always visible when you scroll the page.

Why using flash over HTML5?

Kambi has chosen to build their sportsbook product in Flash (Adobe Flash). To me this is a very strange decision. Why not build it using HTML5 and make it adapt to different form factors. That way it could work just fine on a tablet and smartphones as well.


What people say about this (5)

5 thoughts on “Kambi’s sportsbook is really nice, but why is it built in Flash?

  1. Am not sure the question is valid when considering reuse. There is a whole technology argument and I am all for picking the right technology for the right channel.

    However why would you reuse a web/desktop interface on tablet and mobile? (except maybe as an interim measure?)

    The use of fingers, lack of highlight methods, and actual use case are very different across these channels. Ok so you could make some technology saving with a common core but I think you are always compromising if you are designing one solution across all three channels…

    Tablet can be web-lite or mobile-plus as an interim but web and mobile require very different interfaces in my opinion.

    ps. Great blog as always :)

    • Hi David,

      thanks for your comment. I totally agree with you that you should pick the right technology for the right channel. And I also think as you point out that different form factors require different interfaces. Totally right!

      But I strongly believe that using Flash is a bad choice in this case. I would recommend using HTML5, responsive web design including different CSS’s for different devices, as a complement to apps for the different devices.

      So I am in total agreement with you David :)

  2. I thought I would offer you my account of the decision to go with Flash for this first generation Kambi desktop client. I was and am UX Strategist within Kambi’s UX development team.

    The decision to go with Flash was taken early spring 2010. The feeling among more or less everyone here back then was that we would have liked to go with HTML5 but Flash would have to be the interim choice of desktop client technology because of
    a) The front-end integration challenge, we’re integrating our client into our operator’s HTML and we are basically releasing new version bi-weekly
    b) The then state of uptake of up-to-scratch HTML5 browsers, given the user experience we set out to offer, we would have had to develop quite a number of different versions in order for it to work through-out our operators’ customer base

    Looking back now, we still believe Flash was the right decision for this first generation client. Obviously, we are planning our transition to HTML5 on the desktop as well (we have a HTML5 mobile client up and running) but having done it right away back in 2010 would have given us so much headache that we’re happy with having gone with Flash.

    We are looking for HTML5 talent to hire as well as to take on in full-time consultancy positions. Please turn to to find out more and submit your resume if you fit the bill!

    • Hi Johan,

      thanks for your reply. I can understand that back in 2010 taking a decision to go for HTML5 would be a risky one, and that Flash was probably the right one to go with back then.

      Looking forward to see a HTML5 sportsbook from you guys :)

      Where can I try out the mobile client? Is on Unibet?


      ps. I am a UX Strategist myself but will spread the word about you looking for HTML5 talents. ds.

Join The Conversation

Leave a Reply