Skip to content
Kedgeworks
← All workBetting & gaming2017–18Re-platform

Front-end development on the rebuild of bet365.com.

We worked in the team rebuilding the front end of bet365.com, from December 2017 to March 2018.

Bet365, in public figures
£52.56bn
Wagered by bet365 customers in the year to 25 March 2018
iGamingBusiness, reporting bet365's filed accounts, 2018
77%
Share of bet365's sports revenue that came from in-play betting that year
iGamingBusiness, 2018

These describe the client and the system, not our contribution. What we did is in the sections below.

The situation

Bet365 is an online gambling operator and bet365.com is its site. The front end of that site was being rebuilt, and we joined the work in December 2017, doing front-end development inside an agile team.

Designs came from the UI and UX departments, and working with them was part of the role. That meant helping them annotate a design well enough to build from, telling them where something looked hard to maintain or volatile, and saying what the various platforms being targeted could support.

The constraint

A design had to hold its shape across a lot of devices and browsers, so the unit tests covered the look of the thing as well as the behaviour of it.

Other developers were working in the same front end at the same time, so keeping overlap and regression down meant liaising with them as the work went along.

What we did

We implemented the designs in HTML, CSS3 and TypeScript, and wrote the unit tests that held functionality and design steady across the devices and browsers being supported.

Code review and QA ran every day, alongside the liaison with the other developers on the front end.

What the record supports

Our record names the site, the role and the technology, and it stops there. It does not itemise which parts of the front end we built, and it says nothing about when the rebuild finished or what became of it afterwards.

The technology list runs from HTML5 through to TeamCity without saying what each item was for, and we have left it that way rather than guess. There is no figure attached to this engagement, which is why this page carries none.

Stack
  • HTML5
  • CSS3
  • SASS
  • JavaScript
  • TypeScript
  • Gulp
  • Node.js
  • Selenium
  • Karma
  • Jasmine
  • Mocha
  • Git
  • TeamCity
Related

Working on something similar?