Bede Gaming There’s an app for that
A flexible, open-source platform provider with a single code base, Bede Gaming enables customers to tailor and configure features to different markets. Following the rollout of a new native app, Daniel
Whiteley, Chief Technology Officer, and Jessica Marrs, VP Product Marketing, discuss the ways Bede enhances customer satisfaction and contributes to high scalability for operators across various regions. Dan explains how security is deeply embedded into the platform’s design with multiple layers of protection to ensure robust data safety, meeting the demands of today’s evolving threat landscape.
Bede Gaming unveiled its new native app in Barcelona. How significant an addition is the new app to the company's portfolio and the toolset of clients?
Daniel Whiteley: It's an exciting launch for us. What we're bringing to the market is a brand-new white label app. Initially launching in Germany, the app contains all the key features from the core Bede platform surfaced with content to improve the player experience. Because of how we've architected the new app using a single code base in React Native, we don't have to maintain multiple code bases meaning we can run a lot leaner, quicker, and improve time to market. Te aim is to give our customers something that is out of the box. We still need to configure and tailor but we can achieve that quickly.
Tere are high levels of personalisation with the new app and, because we're effectively on brand new tech, there's no overhead in terms of legacy or tech debt. Change is rapid, yet we can still customise where we need to for specific customer needs. I'm proud of the team in terms of what they've brought to the table. It’s fun building new tech.
Jessica Marrs: From a product perspective, we develop front-end websites for customers where that's required so adding the ability to develop mobile apps for them marries up with the shift we're seeing in player preferences. If you look at industries outside of iGaming, there is a shift towards having apps for various kinds of products and services which is naturally moving into iGaming with a younger demographic. Having the app available in-house allows us to position ourselves as a full-service platform provider across channels, as well
66
as showcase the exciting products we are building, testing, developing and positioning.
Dan, from a technical standpoint, could you walk me through the process of implementing 100+ technology components into an app which works across the full spectrum of mobile and tablets devices?
Dan: Tere's a lot of complexity when you kind of bring in all those different components together. We're starting from a good baseline with the core Bede platform because a lot of these underlying components are stitched in. With the app we're layering it on top. With our modern API architecture, we can integrate API endpoints into our front-end. In this case, a mobile app. A lot of the pain around having to bring that to the surface has already been addressed with the core Bede platform. Tat was a quick win for us in that respect meaning we could have a couple of teams work on building out the new mobile app capabilities. What's the look and feel for players? How do we whitelist this? How do we then build our app into content management systems like Adobe so we can pull real time content in? How do we package that up so we can leverage all the and bolts that sit behind it?
Because of how we've architected our systems, a lot of that complexity has been hidden away in the back-end, allowing us to focus on purely the app and how that should function and feel for the end customer. End to end, the whole process has taken us about six months, but we were delivering value from the get-go through iterative development. We take what we call a 'steel thread' approach in terms of picking a customer journey and working that through and
Page 1 |
Page 2 |
Page 3 |
Page 4 |
Page 5 |
Page 6 |
Page 7 |
Page 8 |
Page 9 |
Page 10 |
Page 11 |
Page 12 |
Page 13 |
Page 14 |
Page 15 |
Page 16 |
Page 17 |
Page 18 |
Page 19 |
Page 20 |
Page 21 |
Page 22 |
Page 23 |
Page 24 |
Page 25 |
Page 26 |
Page 27 |
Page 28 |
Page 29 |
Page 30 |
Page 31 |
Page 32 |
Page 33 |
Page 34 |
Page 35 |
Page 36 |
Page 37 |
Page 38 |
Page 39 |
Page 40 |
Page 41 |
Page 42 |
Page 43 |
Page 44 |
Page 45 |
Page 46 |
Page 47 |
Page 48 |
Page 49 |
Page 50 |
Page 51 |
Page 52 |
Page 53 |
Page 54 |
Page 55 |
Page 56 |
Page 57 |
Page 58 |
Page 59 |
Page 60 |
Page 61 |
Page 62 |
Page 63 |
Page 64 |
Page 65 |
Page 66 |
Page 67 |
Page 68 |
Page 69 |
Page 70 |
Page 71 |
Page 72 |
Page 73 |
Page 74 |
Page 75 |
Page 76 |
Page 77 |
Page 78 |
Page 79 |
Page 80 |
Page 81 |
Page 82 |
Page 83 |
Page 84 |
Page 85 |
Page 86 |
Page 87 |
Page 88 |
Page 89 |
Page 90 |
Page 91 |
Page 92 |
Page 93 |
Page 94 |
Page 95 |
Page 96 |
Page 97 |
Page 98 |
Page 99 |
Page 100 |
Page 101 |
Page 102 |
Page 103 |
Page 104 |
Page 105 |
Page 106 |
Page 107 |
Page 108 |
Page 109 |
Page 110 |
Page 111 |
Page 112 |
Page 113 |
Page 114 |
Page 115 |
Page 116 |
Page 117 |
Page 118 |
Page 119 |
Page 120 |
Page 121 |
Page 122 |
Page 123 |
Page 124 |
Page 125 |
Page 126 |
Page 127 |
Page 128 |
Page 129 |
Page 130 |
Page 131 |
Page 132 |
Page 133 |
Page 134 |
Page 135 |
Page 136 |
Page 137 |
Page 138 |
Page 139 |
Page 140 |
Page 141 |
Page 142
