 All right guys, we'll go ahead and get started This presentation is called real-time mobile e-commerce if you guys are looking for a different session Feel free to go ahead and leave. We won't take offense So a little about us So my name is Ryan Cross. I'm the managing director of cross functional I'm also the Sydney community lead here Organizing the meet-ups and a couple of camps as well have been involved in organizing DrupalCon I've been doing Drupal for about seven years a little over now I've got a few couple of core contributions, but mostly work in the contributed space Jeffrey he may know him as Jeffrey R or Retrovertico on Twitter He's got over four years of experience with Drupal and is a maintainer for several modules He's a senior developer here at cross functional and he's also the the main development lead on the DrupalCon mobile app as well so Cross functional We primarily do a lot of integration work. We specialize in e-commerce mobile development Primarily around consulting Development and training And we're also a platinum sponsor of the event So a little bit of background just a quick show of hands. How many people are actually from Australia or this area? No, Luna Park Okay, quite a few people which is great. Luna Park's a really well-known Icon for Sydney and for those of you that don't know Luna Park is pretty similar to like a Six Flags or Disneyland in terms of the in an amusement park. They've got rides games concerts and events as well Their concert and events is one of the interesting aspects of their business because of the fact that they Have several venues that they run You know commercial events as well as public events As well as they've got restaurants They've got a pool and a few other things that they all managed together under the same same banner Luna Park is also a pretty historical Venue as well It's the it's one of only two amusement parks in the world. That's actually protected by the government and its heritage listed Is originally open in 1935? And it's been a major feature for Sydney's Harbor since then so One of the things that they had in terms of marketing IT They had a lot of really disconnected systems that widely overlapped So people that were actually doing marketing for the events business versus doing marketing for The park itself and other things weren't really connected They also had multiple different systems free commerce So they had an online ticketing system at a separate process for doing gift cards Being able to take online merchandise purchases as well and restaurant bookings. These are all kind of really disconnected But at the same point they had a lot of the same information in them so There existed a kind of major problem for Luna Park Because of these different Disconnected systems. It was really inconsistent amounts of customer information We had 45 actually 47. I think different data sources that we were actually looking at They had customer information. This made it really hard to kind of communicate effectively with for the marketing department They couldn't actually segment their data very well, and they also couldn't really track When they were segmenting who was actually responding back to them very well So really hard to manage any of their marketing campaigns The the other big part to their system was the online ticketing system some of you may be familiar with seat advisor It really for them works well for their concert and event sales But the problem was it really wasn't converting well for a lot of their online stuff Particularly their tickets to the park itself. They had over a 90% fall-off rate In terms of actually getting people through the cart So that ended up being a major concern for them So the main goals of the project and I should probably emphasize that there was multiple projects here It wasn't just a single project But the overall goals were really to kind of allow the marketing team to effectively communicate with their customers being able to segment the data Being able to also Personalize that information in a way that they could actually get a better engagement rate They also wanted to be able to improve the ability to measure and track their customer experience. So Being able to see who's actually come into the park what kind of Response they were having on their marketing campaigns was really important to them as well to be able to make their future campaigns a lot more effective And overall there was a lot of big push to improve the online experience for customers we did some testing of around their existing system and Most people found it extremely confusing and really hard to work with and so that was a big part of improving that So I'm going to cover each of these in a bit more detail But the overall kind of approach that we took was a very integrated approach We wanted to first of all centralize their customer data and make it accessible for them we wanted to provide an integrated e-commerce experience rather than actually have multiple different systems for them and Based off of some other testing. We've realized that mobile experience for them was going to be really important So we tried to optimize for that experience as well and Then based off of what they wanted to do in their marketing We also realized that social media was big a big component for their customer engagement So with a centralized customer view This was actually the first project that we actually kind of came on with Luna Park It's probably a bit surprising for anybody who knows to be CRM to actually see it used in a very strongly commercial context so we CRM is open-source CRM primarily aimed at the nonprofit sector for membership engagement and And kind of fundraising opportunities is tends to be where it actually strives or excels But so we see I'm actually was chosen mainly because the fact that it had the ability to have a relationship Tracking features for families, which was really important to Luna Park. They want to be able to track when their mom comes to Luna Park with their three kids and It made it really difficult to kind of Do that with traditional CRM software because the fact that The kids even though they may have their own email address You couldn't actually use the email address as a unique identifier because the mom would often put the email address In the same field for all all five people or whatever So we had to come up with some unique ways of kind of tracking that And the first pilot project that we did with them was to actually take about ten of those Data sources that they already had and implement those into CV CRM You know we ended up setting up custom fields for each of the different sources And also tracking the authority of each of those different data sources within CV CRM So it wasn't necessarily some of the data sources were going to be kind of archived and Deprecated over time But we wanted to make sure that we could maintain the integrity of this system overall as well so that If you were looking at a piece of information and it can afflicted with a different system You would still be able to kind of backtrack to where that information came from and see which was more up to date or which was more accurate So this was kind of the next big piece the integrated e-commerce And this is going to be to some extent what we focus most of the talk on in terms of the technical side the integrated e-commerce system Primarily consisted of taking that CV CRM system that we had built As well as Drupal using Drupal commerce module by by commerce guys as well as then integrating that with the RR access system called Sanyo so Drupal There wasn't really a huge amount of custom work on in terms of the Drupal side of things We really tried to focus more on the actual commerce side and the user interface side of things The difficult part then was actually then trying to figure out how all that was going to then tie back into the ride access system So Sanyo is a company that actually operates all the tills at the park and Have the ability to actually determine whether or not that That person or that ticket has access to that particular ride because of the fact that Luna Park has Different heights requirements for the different rides and that's embedded in the ticket access control so Through some various bits of research Not only talking with the marketing department, but also talking with users as well We realized that you know mobile particularly in the hospitality sector is a really major focus for them They've got a huge engagement on mobile and that was another big part of why the existing ticketing system wasn't working Is that it didn't work at all on the mobile. There was a lot of things were broken There definitely wasn't a mobile optimized experience And that was a big fall off a big part of the fall off rate as well So The last little bit of this piece as well was then how to actually engage with the customers in A social way as well So Luna Park actually worked with a marketing Company called centric solutions to develop this concept of my experience And the idea basically was that some would actually be able to come to Luna Park Register their ticket for kind of online rewards and then Luna Park will be able to track that customer Throughout the park using an RFID tag Once they have actually then tracked them the customer would be able to share things through their They're my experience account So for example when you would get off of a roller coaster You'd be able to see your photo that would have been taken of you and be able to share that directly on to your Facebook And that wouldn't actually cost the customer anything But then the idea is that knowing does that get shared and improve the experience for the customer But it also gets Luna Park's brand out into social media And then you'll see other people's friends experience that on social media and hopefully complete the circle to come back to Luna Park again So I've got a short little video. This was a promotional video that Luna Park did that probably explains its experience a little bit more Fun is all about sharing sharing heaps of stuff Like the latest apps cool pics Slife's unfun moments and all the good times killing your best mates You're totally set up for it with your smart friends and stuff And now being able to share your experience at Luna Park is really easy Into the brisk code So why wait to tell your friends what you've been up to when you can share it in real-time Simply swipe your wristband to update your status Oh Hands your experience with my experience at Luna Park So as I said, that was the the my experience part of The marketing department the other aspect of it was the Actually, you know, that's the in-park experience We wanted obviously then to be able to get more people to the park and a big part of that was then the actual e-commerce side of that so The idea was to push this This kind of mobile optimized experience so that instead of actually standing in line waiting to get into the park You'd be able to actually again for those of you that are familiar with it You can actually get to Luna Park by crossing the harbor on a ferry So the idea is that you can actually get on the ferry to Luna Park And in the few minutes that actually takes you to actually cross the harbor You can actually go through the checkout process and by the time you get off Everything is ready for you. All you have to do is scan your the barcode on your phone to be able to then get access to the park Otherwise we had problems with well Luna Park had problems with the fact that on really busy days Sometimes people will stand in line for up to two hours So The main results of this kind of integrated approach were really pretty powerful We we worked with them to kind of deliver this integrated marketing platform They actually won an award for the best digital marketing campaign from the International Association of amusement parks We also saw based off of our initial testing and improved customer experience The initial testing and I should probably clarify here the reason why we don't have more concrete Results at this point as we've had a few hardware delays, so it hasn't actually launched yet It should actually launch at least the e-commerce side of this should launch in about a month But the initial testing suggested about 80% or more of the customers can successfully complete the e-commerce without any additional assistance And should really drive the conversion rate a lot higher As I said the conversion rate for a lot of this stuff is still to be fully tested But the main improvement for a lot of this for Luna Park is that it really reduces the wait time for customers and a big part of that as well as it reduces their load on staff and resources by and thereby increases the customer throughput that they can actually get into the park at any given time so I'll do a quick stop right now I've gone through this pretty quickly because I want to give a lot of time for Q&A and also for a demo A bit later, but before I switch over to Jeffrey. Is there any questions on what I've covered so far? No, okay. All right Thank you. Okay so There are several different component as we said before the So the core of the e-commerce site was built on Drupal commerce and we had to sort of sort of customize and build some custom components to sort of make it work with the External Sanyo system, but we also Had in mind to do a few things specifically to target this mobile experience Okay, the Sanyo API of sort of a It's an external system that we sort of Talk to from our end using a custom build sort of soap library well The actual soap library itself was sort of off the shelf PHP software and we just built some custom PHP classes to talk to it sort of to run the Run the various functions that needed while running actually the aim of this was to sort of simplify the process as far as the API was concerned so that Could make the minimum number of transactions between the Drupal site and the API this would sort of cut down on number of points of failure and Would ensure that we would have a more Sort of a more consistent experience from a developer point of view in the beginning there Beginning if I recall correctly there wasn't actually an API to begin with We actually ended up designing the API to integrate with Sanyo Sanyo is a dot net based system built on Microsoft SQL and a bunch of other custom proprietary software. So we designed an API On top of that which then we got the Sanyo implementers to to write and expose to us rather than actually Connecting directly to the database and manipulating things to make sure that the system was more robust long-term and more maintainable We wanted to ensure that there was an API for us to work with rather than trying to manipulate database tables directly Of course between the design and implementation stage. There were a number of changes so we looked into ways to Verify their end of things and to verify that we were using it correctly. So we Took a number of steps to ensure. This was the case We sort of developed a couple of ways of Visualizing the output from the API at our end to make sure that everything was coming through as expected And we used the develop module in some ways there We also developed various unit tests for the module for the API modules we use simple tests to do it and that was Very useful as it turned out because not only did it help us sort of Reliably determine whether the APIs were functioning as expected and whether we were using them properly but it also helped us Managed to pick up some Some bugs and downtime issues okay using Using Drupal commerce as a major boon to us and that it supports multiple payment gateways right out of the box so So we ended up going with secure pay is sort of our main payment gateway but we have the option to add many others including PayPal or any others should we choose it and What payment gateway we end up using doesn't really matter as far as the Sanyo API is concerned as long as it verifies that that payment has gone through that's all good and Of course, we designed the checkout process in such a way that should the that the Customer data was able to be fed into CV CRM with the Requisite indicator of whether they want to be signed up to any mailing lists or anything like that You just note as well that the original spec also and the big reason for the multiple payment gateways being useful is that Luna Park wanted the ability to have the customer allow choice of different payment gateways as well So we've we simplified that for the first launch, but they're gonna roll out a couple of different payment options in the future now for the mobile experience we Actually ended up formulating a particular Particular form of design that was a little bit more than a normal responsive design This I guess we've called responsive design extreme. It's a combination of different things that are informed by multiple different methods We were fortunate enough to be able to do a round of user testing based on the initial only initial layout of the site and we were able to determine a couple of bits of crucial information one of which is that In particular kids seem to be have an innate understanding of a lot of the sort of the conventions of the web but But unfortunately the people with the purchasing power and are not quite as blessed So in a sense, we had to work at providing some alternate visual cues to sort of help people continue through the Continue through the checkout process This would help to sort of reduce friction. Hopefully increase conversion As far as the mobile side of things when we chose a methodology based on Res which is which expands to responsive design plus server side components This is because well, we we determined that while responsive design is really fantastic in terms of sort of Resizing and rebuilding content-based things. It's not necessarily doesn't really suit the way that various application-based sites work and this definitely being a very much app-oriented App-style oriented experience. Sorry This was something we wanted to find ways to improve on and so therefore we tried to figure out ways to Optimize the experience for mobile users including sort of providing more touch-oriented cues of reducing the number of fields various indicators to Ensure that users received more consistent feedback on what was happening and We also ended up building a number of little JavaScript-based tools that would help to emulate a native app experience for instance let's say we have an Have a bunch of markup that essentially renders an accordion on the Desktop version on the mobile version that will render out as a list of links and when you click the list of links an Overlay will pop in from the side showing the content of that accordion pane the similar We got a similar thing to work for forms, too We were able to break it up based on field set and use the headings as links that would essentially pop in the individual components of The form in those field sets as overlays And I'll be demonstrating them a bit later The one other thing I just want to stress that's probably not obvious is that this kind of technique allows the ability to actually have a Significantly different experience on the mobile size browser rather than the desktop based versions But you're still actually using the exact same system in terms of content and delivery But you've got that optimized experience and that's how we went with this approach Okay, the As far as the checkout goes we had to do a fair bit of initial data modeling to account for the the pricing structure of the tickets and to account for the various Upgrades and offers the Luna Park wanted to offer so we so we set out various Pricing rules based on taxonomy various ways of grouping tickets together So for instance, we had a particular taxonomy that So dictated the particular height that belonged to a particular ticket and We also defined another taxonomy that corresponded to the period of the year now this Individ this pricing period could sort of be defined as being a peak period or an off-peak period and Whenever Someone selected a given time of year to visit the park whether it be today or tomorrow or next week or some time in the next three months They would they would see on the list of available tickets once it corresponded to Whatever period was set We also included the facility to Sort of offer add-ons and upgrades for tickets and we we define those using Using node references and and other entity references, so we were able to We were able to Check when a user was going to check out whether they had a particular type of product in their cart and And then see okay. Are there any potential upgrades for this? Ticket are there any potential add-ons and we were able to programmatically display a Form saying do you want to add any of this to your cart? Or do you want to upgrade this particular product? However Since we figured that mobile users were not necessarily interested in going into depth with Their order or anything say they're on the ferry over and they just want to be able to buy a ticket quickly We were we specifically chose to ignore that and we were able to do so by Using some of our client side tools to tell the server and whether or not they're on a mobile device and If that's the case it would just opt to skip those steps entirely and go straight to the checkout page and We were able to use a number of different tools to sort of get that I guess responsive experience at the server and including including just some simple JavaScript Simple JavaScript client detection as well as using detector module and a few other things So if you want to go ahead and So this is the the current design for Luna Park at the desktop version What's probably gonna be easiest for us to kind of demonstrate how some of this will operate is to actually go through the checkout process But actually show how this thing responds on each of the different screens So I probably should actually get out of full screen and then actually be able to change that and you'll see how Who wants to go for it twice? All right, we'll do it twice then okay So one of the things that came out of the user testing was that because of the nature of this ticketing system Or the ticket pricing structure a lot of users were actually really confused about how to actually purchase tickets based off of height so one of the things that we introduced was this kind of ability to educate the users to To kind of teach them that this is how things are going to go in the future And if they have any questions it takes them back to their main corporate site We're all that information that explained in more detail, but it doesn't require us to actually go through it in the checkout process But this is obviously something that'll be Bypass on the mobile version one thing to note of course is that the height indicator only being relevant for Daily tickets is something we were able to skip entirely if someone decided to say go straight for annual annual passes in Future iteration of the site. We're also going to be launching with merchandise So this pop-up window is only relevant for daily passes So this is this is the ability actually then choose a particular date period We gave basically a couple of shortcuts for today and tomorrow and then most of the functionality went into the selecting of the date period This is part of the taxonomy that we were talking about earlier and this actually then allows you to select Based off of this selection you'll get a different list of tickets and different pricing of tickets so you can see here that this was Potentially a bit complicated because not only do you have different types of tickets, but potentially within the different tickets you had different options the way this is actually done is using Products or people familiar with triple commerce a product display node is actually in each Accordion screen and then the different product variants are what actually then go vertically in that table and that that is also dependent on the different types of products that we're using as well and It may sound easier to actually ride a lot of the stuff kind of hard-coded and Simplified but because of the fact that Luna Park is constantly changing their tickets We needed to make a system that was going to be flexible enough that they could actually get these kind of Displays without having to constantly rebuild them You can see there gets you a little notification that you've added to your cart you get the cart on the side That's all pretty standard triple commerce functionality So you can see the different types of tickets then have a different type of display And all of the text is obviously user editable so they can also introduce images or other kind of marketing promotions For the same point all a lot of this information then is actually linked to The actual ticketing ticket accessing system Sanyo to pull that information in a lot of these fields are pretty standard Experiences when you're actually working with triple commerce There are a couple of unique things so for example being able to insert the terms and conditions as well as we inserting a custom field to actually determine whether or not the user wants to be signed up to various Luna Park mailing lists And I forgot to mention as well at the beginning that this all of this at the moment was actually Being hosted with our partner anchor Which you may have seen downstairs. They're also sponsoring triple triple con However, I'm running this over my phone So that the delay on here is more than likely because of my phone internet connection not because of their hosting And I'll probably point this out on the next go around But for those that haven't you may look at also the checkout process and how the buttons actually change So one of the other things that we needed to be able to do to improve the customer experience was conditionally change What actually? And so once you've actually completed You also get a nice little checkout complete Now this particular purchase we've purchased 20 different tickets so you can actually download the individual tickets as a PDF And you'll then be able to actually get a barcode Which then when you actually take through the park, you'll actually be able to scan and I'll talk about a few other things As well One of the things that will be coming in future versions of this as well is the ability to actually have a more personalized Online experience as well. So right now. We're not actually even though we're collecting all of the information and Being able to store that in the CRM for future marketing opportunities. We're not actually creating an account for them in Take it back the latest version take it back. We are actually creating the account for them The first version is we didn't actually create accounts, but we are creating accounts now to allow them to actually Reclaim their tickets, but the next version is also expected to have a more personalized experience where they can be able to Customize what types of notifications they want to be or what type of mailing list that they want to be involved in as well as getting Games online specifically for Luna Park and those kind of things as well and develop the more Mature online experience. So this is the mobile experience You notice the first page is not significantly different, but it'll it's obviously optimized smaller graphics and Things move down below But now you'll begin to see that things are quite different instead of actually having a longer table You get to be able to actually see how these things become list items and use kind of more native style Widgets we should probably go back through and show them how to select how the different. Yeah So you can see this is a completely different style So instead of actually having just a you know a button or whatever else this actually becomes a drop-down And then you get the same options as you would in the desktop version, but the experience is obviously optimized for touch The buttons are obviously bigger. There's a stronger Touch element for them and then you'll see here There's also a lot of things that are probably hidden which you probably would have noticed in the desktop version So the little sidebar helper around the different height restrictions and those things Those have all been kind of hidden Passed away and when you actually open up the various tickets Instead of actually having the same kind of graphical issue You actually then have a more streamlined mobile experience where you can actually then pick from there and you don't actually enter in The quantity that you want you just Add individual into your cart considering that you're unlikely to buy bulk purchases on your mobile phone You're more than likely to just buy a few or one Okay You can see the shopping cart is now also moved to the bottom since it's a secondary piece of navigation And then the shopping cart experience now when you actually go to check out One of the things that we realized on the mobile experience is that it's really a poor experience to have the same You know, you still need the same number of fields Getting a really really long scrolling list of fields on a mobile experience is really poor So we broke it up in a way that allows people to actually enter it in in piece wise And they don't get scared about actually having to enter in so much information And then we visually indicate when they've successfully completed each little piece of the form And so you can see there that the different visual indicators on the right You get a final chance to review your order Which is all pretty standard stuff putting your credit card details and then you complete your order Okay So now you actually have a different style of the completion page even though the information again is the same So you get some information about what is good to bring if you for example are not actually already on your way Get the ability to also share that information with your friends in terms of social media and Park information the last bit is to actually then view your tickets actually on your phone and be able to actually then get into the park with that and this This is gonna be further optimized than before we actually release it. This is still kind of Dummy marketing material But then you'll be able to actually scan this at the park that covers most of the demo No, no There there was some issues That we had to deal with in terms of the standards of the different barcodes. So as long as we actually use One of the standard barcodes doesn't really matter about the scale So, yeah, but we did we did fight some of the standards initially So some next steps as I mentioned earlier a lot of this other stuff is already launched so CV CRM is already there The my mark my experience stuff has already been implemented and the e-commerce stuff is developed But it's the last piece that hasn't really been launched yet So that's going to be launched in approximately the next couple of weeks probably a month just when we finish Deal with a few minor harbor issues The other big piece then is then to finish centralizing the CRM to integrate with the my experience And other data sources which will allow further kind of in-park marketing opportunities The idea is once all of this stuff is integrated and tied together When somebody actually Buy something online all that information is in the CRM. They come to the park. They'll be able to then Register for my experience and then you'll be able to do marketing opportunities for example when somebody actually gets off of the Roller coaster they've come out You'll be able to actually see and know that they've just come off So they're right next to the food court be able to then SMS them a 10% discount for food and be able to market them In a way that can hopefully drive more business within the park as well so As well as and that's just one really specialized example, but there's obviously tons of opportunities there But this often that this then provides a platform for them to do a lot of different creative marketing opportunities As well as better manage their customer experience because obviously that's the best the end game so That's it if anybody's got any questions we've got I think just about 15 minutes, so we're doing well on time Yes There was a few few struggling pieces One of the things it was difficult to begin with was that this the city CRM component actually started a little over a year ago about a year and a half ago so about Halfway through some of the stuff that we were doing with the e-commerce stuff We realized that we needed to actually upgrade To a significant major version of city CRM But that actually helped us a lot because the older version of city CRM was harder to work with The newer version of city CRM had a much better API in terms of the web services and stuff and also allowed us the ability to Make it easier for some of the future integrations we want to do to actually link So this is connected to their commerce website and we'll also then be connected to their their main corporate site But they've got a set of I think about another nine different websites that they all want to Pull their information into city CRM from So that's going to make that a lot easier However There was also a little bit of struggle with the fact that City CRM is kind of geared towards Non-profits rather than kind of a commercial side of things. So I see a little bit of Potential in the future for there to be some limitations Just because the fact that one of the things that they want to pull in is their actual sales team from the events Department and because the city CRM doesn't really have a sales pipeline kind of method built into it There's going to probably be a little bit of custom software that needs to be written there To provide a proposal system within city CRM Does that answer your question? It is I mean, I guess the point I would probably make there that right now We're only doing one way integration or you know in terms of the city CRM component So it's only data coming into city CRM And so but there and that's definitely the next piece that I mentioned for the city CRM integration is Getting a lot of these other data sources to come in and actually doing two-way integration for those That's you know, we didn't want to kind of tackle the super hard problem first We want to tackle the easy one and see if it actually worked well particularly because a lot of those Data sources we're trying to cut it down. I mean Even even half of that Going from 45 to 25 would be a big improvement just in terms of manageability But We'll see you where you go Yeah, I'll let Jeffrey that's probably Okay Yes, and no some of the content is just being shown or hidden and you can do that with simple media queries We some extent. Yes, we use simple media queries But we also use a JavaScript based method in which we try and detect the use size of the browser and a couple of other aspects and Moreover in the case of those sort of more complex user interface bits such as working with the accordion and the list of items We use that we try and use the JavaScript based size detection to To Determine what aspect we should be displaying and then we sort of essentially initialize the proper widget for that aspect and Pretty much, but we try and keep the markup as lean as possible to ensure that it's not there's not too much overhead I should add one other thing that we didn't actually use on this project But has come out of some of this work, which is a module Contributed back to the triple community called detector and it's a really cool little module for doing some of this stuff because it allows you to Detect different properties of the browser and screen size is one of them and then conditionally Change what you're going to do. So we built in the ability to actually Alter it based off of context module and I think there's also some rules integration as well So you can do a lot of kind of really basic things using that Without a whole lot of additional effort on the front end if you want to go down that path Still need to do a bit of work on it before it's ready for primetime there Okay, the price variation with taxonomy It's probably explained like this the Essentially we have several different variations of Product per sort of product display if you will the product displays are a type of node and the product variations are essentially a commerce specific entity that are linked from the product display and We have different prices on all those variations and that's pretty much how we are able to Sort of modify the price like that you would able to you'll be able to do the same sort of thing by say having Say if you're selling cushions or something if you want to sell different sizes You would set up size as a given taxonomy and assign different terms to your different product variations and you could do the same with colors or Pretty much any other property you feel like I Think one of the things that you may also be asking about is how does the taxonomy choice then drive the tickets? The taxonomy Choicing that we're actually doing is actually based off of the date and so the all of the different prices are represented as different variations We're not actually changing the price based off of the taxonomy It's the other way around based off of the taxonomy that they choose We then choose or we selectively display different product variants that they use Okay. Yeah, there was a few things. I mean we actually had a big debate about the upgrade and add-on process And whether we should completely remove it At all and kind of try to do it maybe only in like a sidebar kind of thing But at the same point from the commercial side Luna Park that became something that they really wanted to actually have So we did our best to really minimize the number of clicks But also needed to make it a bit flexible so they there's basically The basic case right now is that any ticket that you actually buy They want to give you the option to actually upgrade it to an annual pass And it's actually I mean it makes commercial sense even from a consumer perspective because buying a ticket to like a standard ticket is like $49 or something like that and getting an annual pass is 99 dollars So if you're gonna go there at all more than once it definitely makes sense And a lot of and that was part of the research that we found is that a lot of people Because they have all these different pricing things a lot of people got really confused So in some regards actually presenting them the upgrade Was actually a benefit to them. We had somebody actually come through our user testing who had been to Luna Park like ten times over the last two years and So it was obviously very familiar with Luna Park And she had no idea that she could actually save so much money by getting an annual pass And she only found that out after going through our user testing and realized oh, there's this option to do this And I've been doing it this way for so long so From that perspective we kind of that's how we went down that path. Does that answer your question There was on to that point as well The one thing that they probably did influence that was the completion page our initial completion page was Particularly for the desktop was a lot more informative There was a lot more links to other things in the park and information that kind of stuff and after we kind of Really like stripped out a lot of that stuff for the mobile version We kind of went back and looked at the desktop version was like wow this is way too much And so there was definitely their stuff there that we pulled out. I'm sorry. I can't hear you can speak up So the question is sending the tickets to passbook on the iPhone No, we didn't or at least not yet. It's definitely something I guess we can look at but that being said One of the things we really wanted to make sure with this approach as well is that it's kind of device agnostic so You know the way for example that we did the Drupalcon mobile app We actually did a lot of stuff based off of HTML in the back end But then each platform has their own build It was really important for us to be able to give this experience to users Without necessarily having to determine or lock them to a particular device So again kind of a small example We didn't expect this at all but in part of our user testing somebody happened to come in with a blackberry Which is something we had not even factored into our requirements at all And he pulled it up and it more or less worked fine There was a few small CSS tweaks that we needed to do just on a few little buttons and stuff and that was That was it. So we were really excited to see that that kind of cross device opportunity was there But I will look into the the playbook Any other questions? Who wants to go to Luna Park? Sorry, was there a final question there? All right Well, if anybody really if anybody really actually is interested in going to Luna Park We'll definitely kind of arrange something We'll I'll talk to to the guys there and see if we can actually get something organized for later this weekend I'm sure they'll be Happy to have us All right. Well that pretty much wraps us up. We've got about two minutes left unless there's any final questions Okay, great. Thanks guys