High Level Overview
Eyas Gaming, responsible for the development of Merkur’s online products, brought me in to take responsibility for the end to end development of the apps.
Strategy
We sought to understand Merkur’s target market in relation to the brands we would include as part of the whitelabel, and created a product consistent with the high standards our players expected.
Whitelabel Development
I was responsible for shaping the whitelabel to ensure maximum flexibility across brands and markets. I did this by creating a strong CMS from which a number of features could be configured, allowing for maximum flexibility.
Fully Agile
The start-up culture at Eyas allowed me to develop the apps in a fully Agile environment. This meant the delivery process was dynamic and adaptable optimising the development process.
Budget Management
I was responsible for overseeing the development of the apps in relation to the budget and identifying any delays or challenges that may affect costings; and adjusted development accordingly.
End-to-End Dev
I managed the iOS and Android apps, building them from the ground up.
Compliant List View
Worked with UX to design a reimagined listview as per Apple’s Review Guidelines
Enhanced QA
Worked with in-house testers on extensive QA and UAT, as well as writing procedures.

App Marketing
I led the dev for push, IAM, web app banners and mobile attribution.
Full Feature Set
This included navigation, games, recently played, on-boarding, account and more…
Store Management
Worked with the business to create developer accounts and submit the apps.
Some more information…
Eyas offered me the opportunity to build a hybrid app template which allowed backend flexibility in tailoring the product to the target market.
What was the strategy and vision for the development of the apps from scratch?
After ensuring compliance with licensing regulation and Apple’s Guidelines was achieved, my focus was on user experience and building a strong back-end. This would allow the business to easily configure the app’s features and look and feel across the company’s upcoming brands, tailored to specific demographic. I set about achieving this by adopting a data-driven approach, which sought to first understand user behaviour through analytics and A/B testing, and building configurability into the CMS to accommodate on the fly refinement of the front-end without the need for re-submissions using remote config.
I set about achieving my vision by writing the requirements myself, and planning the phases of development, before working with delivery teams (app and web where dependencies were identified) on estimating work and planning the sprints and refining the backlog as the development panned out.