WEBVTT 00:00:00.000 --> 00:00:02.155 >> Hi, my name is Adam Tuliper. 00:00:02.155 --> 00:00:04.150 Welcome to GDC, this is an exciting week. 00:00:04.150 --> 00:00:06.060 We have lots of very exciting interviews. 00:00:06.060 --> 00:00:07.060 That we're going to be doing this week, 00:00:07.060 --> 00:00:08.260 across mixed reality, 00:00:08.260 --> 00:00:09.925 across game development. You name it. 00:00:09.925 --> 00:00:11.100 We're going to be talking to folks here. 00:00:11.100 --> 00:00:12.265 All the interviews are going to be 00:00:12.265 --> 00:00:13.675 doing here live at GDC 00:00:13.675 --> 00:00:15.290 are going to be posted online afterwards. 00:00:15.290 --> 00:00:16.550 You can stop by our booth 00:00:16.550 --> 00:00:17.670 and join us for some of this, as well. 00:00:17.670 --> 00:00:19.445 I think we have some exciting times coming ahead. 00:00:19.445 --> 00:00:21.560 So I look forward to seeing you all this week. 00:00:21.560 --> 00:00:24.220 Today I'm here with Brendan Vanous from PlayFab. 00:00:24.220 --> 00:00:26.620 There's has been some recent exciting news 00:00:26.620 --> 00:00:28.030 that's happened at PlayFab. 00:00:28.030 --> 00:00:29.720 I was excited to hear this. 00:00:29.720 --> 00:00:32.060 So, back in January there was 00:00:32.060 --> 00:00:33.400 an acquisition that happened and 00:00:33.400 --> 00:00:34.975 PlayFab is joining Microsoft. 00:00:34.975 --> 00:00:37.075 Can you talk about what is PlayFab? 00:00:37.075 --> 00:00:39.090 What makes up PlayFab? What's so exciting about that? 00:00:39.090 --> 00:00:41.710 >> Yeah absolutely. So PlayFab is, 00:00:41.710 --> 00:00:45.080 effectively, a complete back end for video games. 00:00:45.080 --> 00:00:47.440 It's everything that's fundamental to 00:00:47.440 --> 00:00:49.600 the needs of game developers, in the cloud. 00:00:49.600 --> 00:00:51.760 So you've got authentication systems, 00:00:51.760 --> 00:00:53.130 you've got data systems, 00:00:53.130 --> 00:00:54.580 catalogues of goods, in 00:00:54.580 --> 00:00:56.685 app purchasing, receipt validation. 00:00:56.685 --> 00:00:59.655 And then, layered on top of all of those, 00:00:59.655 --> 00:01:01.690 what you might think of as the fundamental components, 00:01:01.690 --> 00:01:03.830 we've got what we call playstream, 00:01:03.830 --> 00:01:06.465 which is all the event data coming in for your game. 00:01:06.465 --> 00:01:08.800 Coming in in real time. The events 00:01:08.800 --> 00:01:09.810 are coming from clients, 00:01:09.810 --> 00:01:11.780 from servers, from third party integrations, 00:01:11.780 --> 00:01:14.090 and it's sort of 00:01:14.090 --> 00:01:16.310 if you think of the modern serverless computing model, 00:01:16.310 --> 00:01:18.150 it's all of this event data that flows in, 00:01:18.150 --> 00:01:19.400 and then there's consumers on 00:01:19.400 --> 00:01:20.910 the stream that are there to 00:01:20.910 --> 00:01:24.090 be enable a wide range of LiveOps capabilities. 00:01:24.090 --> 00:01:27.495 So that games can be engaged with their players and, 00:01:27.495 --> 00:01:28.980 you know, make the game experience 00:01:28.980 --> 00:01:29.720 new and fresh all the time. 00:01:29.720 --> 00:01:30.470 >> To the next level. 00:01:30.470 --> 00:01:31.295 >> Yeah exactly. 00:01:31.295 --> 00:01:32.820 >> Interesting you mention the term 00:01:32.820 --> 00:01:33.930 LiveOps and so this is 00:01:33.930 --> 00:01:35.380 a term that you started to hear more of now in 00:01:35.380 --> 00:01:37.140 game development and game operations. 00:01:37.140 --> 00:01:38.780 What exactly is LiveOps? 00:01:38.780 --> 00:01:42.190 >> So LiveOps it's short for live game operations. 00:01:42.190 --> 00:01:43.990 And it's everything that you 00:01:43.990 --> 00:01:45.975 do with your game that's not like, 00:01:45.975 --> 00:01:47.995 it's not about new features. 00:01:47.995 --> 00:01:49.550 It's more about the things that you 00:01:49.550 --> 00:01:52.000 do that are there to make 00:01:52.000 --> 00:01:54.240 the experience continuously updated 00:01:54.240 --> 00:01:56.095 and fresh and personalized. 00:01:56.095 --> 00:01:58.065 So in part, it's things like, 00:01:58.065 --> 00:01:59.420 you know in-game events. 00:01:59.420 --> 00:02:01.250 Like you know hey we just had a bunch of 00:02:01.250 --> 00:02:03.160 games do St. Patrick's Day that's right 00:02:03.160 --> 00:02:03.900 >> Yes true. 00:02:03.900 --> 00:02:05.920 >> So you know there are special St. Patrick's Day 00:02:05.920 --> 00:02:06.980 and maybe there were new 00:02:06.980 --> 00:02:08.370 costumes that are available for that. 00:02:08.370 --> 00:02:09.400 Things that you can only get during 00:02:09.400 --> 00:02:10.475 the brief window of time. 00:02:10.475 --> 00:02:12.790 So it really incentivizes players to jump in and 00:02:12.790 --> 00:02:14.030 be part of the experience 00:02:14.030 --> 00:02:15.735 during that window of opportunity. 00:02:15.735 --> 00:02:17.425 But it's also about 00:02:17.425 --> 00:02:21.005 focusing on the different ways that people play games. 00:02:21.005 --> 00:02:22.560 So user segmentation is 00:02:22.560 --> 00:02:24.885 a common term that you hear in live game operations. 00:02:24.885 --> 00:02:26.235 And it's all about finding 00:02:26.235 --> 00:02:28.700 all the different ways that people engage with the games, 00:02:28.700 --> 00:02:30.875 categorizing them and then 00:02:30.875 --> 00:02:32.800 using all the different segments that a player 00:02:32.800 --> 00:02:34.180 is part of in order to 00:02:34.180 --> 00:02:37.055 personalize the experience as much as possible for them. 00:02:37.055 --> 00:02:39.950 And the goal. I mean the big goal we talk about is 00:02:39.950 --> 00:02:42.840 getting to the segment of one. Which has been. 00:02:42.840 --> 00:02:44.130 >> Segment of one, whats that? 00:02:44.130 --> 00:02:45.515 >> Yeah its being able to say that 00:02:45.515 --> 00:02:47.755 I have identified enough things about you. 00:02:47.755 --> 00:02:50.380 That I can treat you as an individual player. 00:02:50.380 --> 00:02:51.390 There might not be another player in 00:02:51.390 --> 00:02:52.440 the entire game that 00:02:52.440 --> 00:02:53.920 plays the game the same way that you do. 00:02:53.920 --> 00:02:55.250 I mean, that's pretty 00:02:55.250 --> 00:02:57.450 high reaching blue sky kind of goal. 00:02:57.450 --> 00:02:59.630 But you know that is the idea. 00:02:59.630 --> 00:03:01.430 >> And so then you can tailor the experience for 00:03:01.430 --> 00:03:04.910 that particular type of user, that single user. 00:03:04.910 --> 00:03:08.660 >> So a simple example of that would be. 00:03:08.660 --> 00:03:11.050 Like we have a store system. 00:03:11.050 --> 00:03:13.040 So you would have a catalog goods and 00:03:13.040 --> 00:03:15.135 then for the catalog you have a set of stores. 00:03:15.135 --> 00:03:16.820 And each of the stores has 00:03:16.820 --> 00:03:18.875 a different way to represent some set of items. 00:03:18.875 --> 00:03:21.445 And so what you can do is you can change 00:03:21.445 --> 00:03:23.140 which stores are showing to players 00:03:23.140 --> 00:03:25.165 based on what user segments they are in. 00:03:25.165 --> 00:03:27.450 So, the comparison is 00:03:27.450 --> 00:03:29.200 to like the concept of a grocery store. 00:03:29.200 --> 00:03:30.890 The grocery store has like an eyeline. 00:03:30.890 --> 00:03:32.630 The eyeline is where they put the product that they make 00:03:32.630 --> 00:03:33.430 their most profit on 00:03:33.430 --> 00:03:35.105 because that's they want to sell to the most. 00:03:35.105 --> 00:03:36.480 But in the case of players, 00:03:36.480 --> 00:03:38.495 different players want to see different things. 00:03:38.495 --> 00:03:41.100 Like a player who's never really purchased as much. 00:03:41.100 --> 00:03:44.075 He probably want see just a couple of 99 cents items. 00:03:44.075 --> 00:03:46.510 Whereas somebody who spends a lot of money in 00:03:46.510 --> 00:03:48.955 games frankly doesn't want to sell 99 cents items. 00:03:48.955 --> 00:03:50.935 They want to sell at ninety nine dollars thing that has 00:03:50.935 --> 00:03:52.800 a million gold and the Sword of 00:03:52.800 --> 00:03:54.535 Doom you know that's because. 00:03:54.535 --> 00:03:55.710 >> We have a lot of users right. 00:03:55.710 --> 00:03:55.930 >> Yeah. 00:03:55.930 --> 00:03:57.455 >> Interesting. So tailoring 00:03:57.455 --> 00:03:58.720 the experience for that user 00:03:58.720 --> 00:04:00.470 to maximize their engagement. 00:04:00.470 --> 00:04:03.060 Hopefully if you have the net purchases kind of pull a 00:04:03.060 --> 00:04:04.140 little bit more of that out of them 00:04:04.140 --> 00:04:05.410 for that particular user types. 00:04:05.410 --> 00:04:07.575 Some might be into that that some might not interested. 00:04:07.575 --> 00:04:10.530 Now, as part of the Microsoft acquisition, 00:04:10.530 --> 00:04:11.925 we'll take a step back. 00:04:11.925 --> 00:04:14.175 I'm a developer, I love development technologies 00:04:14.175 --> 00:04:15.640 and I think one of the things that we try 00:04:15.640 --> 00:04:18.570 to focus on in Microsoft is really supporting developers 00:04:18.570 --> 00:04:19.980 anywhere regardless of your platform. 00:04:19.980 --> 00:04:20.390 >> Yes. 00:04:20.390 --> 00:04:21.760 >> We want to support developers on iOS. 00:04:21.760 --> 00:04:23.980 We want to support developer on Android. 00:04:23.980 --> 00:04:24.470 We want to support 00:04:24.470 --> 00:04:26.130 developers if you're developing on the switch. 00:04:26.130 --> 00:04:27.790 So as part of 00:04:27.790 --> 00:04:28.570 this acquisition will you be 00:04:28.570 --> 00:04:29.680 dropping any of your platform? 00:04:29.680 --> 00:04:31.225 >> No, no absolutely not. 00:04:31.225 --> 00:04:32.610 We've worked closely with 00:04:32.610 --> 00:04:34.170 our partners at the various platforms to 00:04:34.170 --> 00:04:35.580 make sure that we will continue to 00:04:35.580 --> 00:04:37.370 support them in the same way that we have to date. 00:04:37.370 --> 00:04:39.890 Because frankly, we want to 00:04:39.890 --> 00:04:42.665 be there for all games, all platforms. 00:04:42.665 --> 00:04:45.200 We are you know, platform agnostic. 00:04:45.200 --> 00:04:46.030 >> It's good. 00:04:46.030 --> 00:04:48.990 >> And we just want to be the thing that you're able to 00:04:48.990 --> 00:04:50.320 use to drive those experiences 00:04:50.320 --> 00:04:51.810 regardless of where you are and where your players are. 00:04:51.810 --> 00:04:53.510 >> That's great whatever tools whatever development 00:04:53.510 --> 00:04:55.230 technologies you want to support them wherever we are. 00:04:55.230 --> 00:04:57.150 So we are- we are aligned in 00:04:57.150 --> 00:04:58.420 that- in that vision which is 00:04:58.420 --> 00:04:59.710 amazing for right developers. 00:04:59.710 --> 00:05:00.400 >> Thats great. 00:05:00.400 --> 00:05:03.425 >> Now also as an indie developer myself. 00:05:03.425 --> 00:05:04.970 For me things that matter a lot 00:05:04.970 --> 00:05:06.180 were free tiers of products. 00:05:06.180 --> 00:05:06.450 >> Uh yeah. 00:05:06.450 --> 00:05:08.650 >> And so, will you be keeping your free tier. 00:05:08.650 --> 00:05:10.135 >> Exactly, Yeah yeah. 00:05:10.135 --> 00:05:11.760 The free tier is really important to us. 00:05:11.760 --> 00:05:14.150 I mean. When you look at 00:05:14.150 --> 00:05:15.460 the games industry in general you've 00:05:15.460 --> 00:05:17.125 got a range of different developers. 00:05:17.125 --> 00:05:20.240 And fundamentally, in order to have 00:05:20.240 --> 00:05:24.380 a healthy you know game development environment 00:05:24.380 --> 00:05:27.450 across the global scope. 00:05:27.450 --> 00:05:29.215 You need the support indie developers. 00:05:29.215 --> 00:05:31.010 Indie developers are where you're going to get some of 00:05:31.010 --> 00:05:32.810 your craziest freshest new ideas. 00:05:32.810 --> 00:05:33.460 >> Absolutely. 00:05:33.460 --> 00:05:34.840 >> And some of the most interesting 00:05:34.840 --> 00:05:36.030 new developments in game play, 00:05:36.030 --> 00:05:37.625 right and game play models. 00:05:37.625 --> 00:05:39.890 So yeah, we really want to encourage 00:05:39.890 --> 00:05:41.130 indie developers and so we will 00:05:41.130 --> 00:05:42.905 always be keeping our free tier. 00:05:42.905 --> 00:05:45.200 You know, we we're- we're doing what we can to 00:05:45.200 --> 00:05:47.275 expand the capabilities of it as much as possible. 00:05:47.275 --> 00:05:48.610 Obviously you know, we've got to 00:05:48.610 --> 00:05:49.960 control costs a little bit. 00:05:49.960 --> 00:05:51.090 But it's always going to be there 00:05:51.090 --> 00:05:52.100 so the developers will be able to 00:05:52.100 --> 00:05:54.370 get their games to market and not have to worry about, 00:05:54.370 --> 00:05:56.215 you know ah my god my my game got 00:05:56.215 --> 00:05:58.295 featured on this really popular site. 00:05:58.295 --> 00:05:59.340 Now I've got a million users. 00:05:59.340 --> 00:06:01.430 How to pay for this. We don't 00:06:01.430 --> 00:06:02.590 want to have people have to worry about that. 00:06:02.590 --> 00:06:03.800 >> That's good. Well so 00:06:03.800 --> 00:06:05.300 speaking of tiers you have a free tier. 00:06:05.300 --> 00:06:06.160 Can you walk through 00:06:06.160 --> 00:06:07.670 what the other tiers that are involved? 00:06:07.670 --> 00:06:10.270 >> Sure. Yeah. So in addition to the free tier, 00:06:10.270 --> 00:06:12.160 we actually also have an indie tier which is 00:06:12.160 --> 00:06:15.135 specifically for small indie companies. 00:06:15.135 --> 00:06:16.570 They need a little bit 00:06:16.570 --> 00:06:17.730 more and then they can get 00:06:17.730 --> 00:06:18.760 in the free tier.The free tier, 00:06:18.760 --> 00:06:20.230 I mean it's- it's you know it's a little 00:06:20.230 --> 00:06:22.330 limited in terms of the resource availability, 00:06:22.330 --> 00:06:24.545 but it's not limited in terms of number of users. 00:06:24.545 --> 00:06:25.480 I need to be clear about that. 00:06:25.480 --> 00:06:27.535 No tier is limited in number of users. 00:06:27.535 --> 00:06:29.795 But yeah in the indie tier 00:06:29.795 --> 00:06:32.090 it gets them some higher limits. 00:06:32.090 --> 00:06:33.600 It still doesn't provide 00:06:33.600 --> 00:06:35.585 the same private support 00:06:35.585 --> 00:06:37.510 for example the professional tier does. 00:06:37.510 --> 00:06:39.500 But it get a little bit more resource capability. 00:06:39.500 --> 00:06:40.840 The professional tier then 00:06:40.840 --> 00:06:42.470 is for companies that are established, 00:06:42.470 --> 00:06:45.160 they've already had submitted titles and that's 00:06:45.160 --> 00:06:48.275 where we introduce a MAU base. 00:06:48.275 --> 00:06:50.905 So per MAU, monthly active user base, 00:06:50.905 --> 00:06:52.800 is the way we do pricing on that. 00:06:52.800 --> 00:06:55.550 We keep those prices as low as we possibly can. 00:06:55.550 --> 00:06:57.300 We're always looking for ways to optimize. 00:06:57.300 --> 00:06:58.970 But in the pro tier that's where we 00:06:58.970 --> 00:07:01.145 then have private support. 00:07:01.145 --> 00:07:03.240 We have a service level agreement things like that. 00:07:03.240 --> 00:07:05.310 And of course our largest customers, 00:07:05.310 --> 00:07:07.465 we have an enterprise tier 'which is really, 00:07:07.465 --> 00:07:09.790 that's more about sort of custom relationship 00:07:09.790 --> 00:07:11.220 between us and our biggest customer. 00:07:11.220 --> 00:07:12.930 >> So is it really based on all MAUs. 00:07:12.930 --> 00:07:13.650 I've heard that term a lot 00:07:13.650 --> 00:07:14.990 lately has it all based on MAUs, 00:07:14.990 --> 00:07:16.380 the monthly active users. 00:07:16.380 --> 00:07:18.440 >> The core services are all MAU based. 00:07:18.440 --> 00:07:21.435 Yes, when you talk about the professional tier. 00:07:21.435 --> 00:07:24.860 And but in addition to the core service, 00:07:24.860 --> 00:07:28.005 we have a few things that are usage based cost. 00:07:28.005 --> 00:07:30.335 Which is really it's dedicated server hosting, 00:07:30.335 --> 00:07:32.850 its CDN usage and of course we have 00:07:32.850 --> 00:07:35.175 a whole addon marketplace of 00:07:35.175 --> 00:07:38.315 third party technologies that we integrated into PlayFab. 00:07:38.315 --> 00:07:39.760 So that we make those available to developers. 00:07:39.760 --> 00:07:40.190 >> That's really true. 00:07:40.190 --> 00:07:42.040 >> A lot of those are free. I mean all of the platform 00:07:42.040 --> 00:07:44.555 iOS and Android and all of those platforms are free. 00:07:44.555 --> 00:07:46.800 But there's a few where there's 00:07:46.800 --> 00:07:47.960 some charge from the third party 00:07:47.960 --> 00:07:49.150 like Catalpa for example. 00:07:49.150 --> 00:07:51.980 >> Now at Microsoft we've been pretty 00:07:51.980 --> 00:07:55.600 focused over the years on Windows and XBox. 00:07:55.600 --> 00:07:57.630 Now we try to enable developers anywhere. 00:07:57.630 --> 00:07:59.190 What assurances do developers 00:07:59.190 --> 00:08:00.900 have that are currently on PlayFab, 00:08:00.900 --> 00:08:03.450 that the support for them is going to stick around, 00:08:03.450 --> 00:08:04.990 that PlayFab is going to stay around? 00:08:04.990 --> 00:08:06.870 >> I mean, I hear that a lot. 00:08:06.870 --> 00:08:08.825 I mean I'll be honest. I hear that from a lot of people. 00:08:08.825 --> 00:08:11.280 But fundamentally, if you look at 00:08:11.280 --> 00:08:12.970 the gaming market and you look 00:08:12.970 --> 00:08:16.115 at the addressable space in the market. 00:08:16.115 --> 00:08:18.795 You can see that it's you know, there's console, 00:08:18.795 --> 00:08:21.125 there's steam, there's HTML five web games 00:08:21.125 --> 00:08:22.485 there's mobile games. 00:08:22.485 --> 00:08:27.815 It's all part of the total economy space of games. 00:08:27.815 --> 00:08:32.380 Microsoft is clearly committed to being across all of it. 00:08:32.380 --> 00:08:36.660 I mean if you look at the blog posts by Creme, 00:08:36.660 --> 00:08:39.495 Crème Chowdry our Executive Vice President, 00:08:39.495 --> 00:08:42.610 by Phil Spencer, our ADP excuse 00:08:42.610 --> 00:08:46.275 me and even if I have to search an [inaudible]. 00:08:46.275 --> 00:08:48.735 Look at the quarterly business reports right. 00:08:48.735 --> 00:08:50.095 They're all calling up the same thing. 00:08:50.095 --> 00:08:53.090 That games is now a fundamental pillar of Microsoft. 00:08:53.090 --> 00:08:53.655 >> Absolutely. 00:08:53.655 --> 00:08:56.205 >> So it previously was part of the windows organization. 00:08:56.205 --> 00:08:58.130 But now it still reports directly to [inaudible]. 00:08:58.130 --> 00:09:00.230 So there's a level of investment there that 00:09:00.230 --> 00:09:03.050 makes it clear that Microsoft is all in on us. 00:09:03.050 --> 00:09:04.840 >> So, again as 00:09:04.840 --> 00:09:07.365 a developer and loving Game Dev technologies, 00:09:07.365 --> 00:09:10.870 being part of Microsoft, I can't tell you I'm super 00:09:10.870 --> 00:09:12.360 excited to see the engagement 00:09:12.360 --> 00:09:14.140 that we've had in gaming platforms. 00:09:14.140 --> 00:09:16.980 Kind of this new game killer that's 00:09:16.980 --> 00:09:19.170 been focused and the resources 00:09:19.170 --> 00:09:20.875 assigned to it is super exciting. 00:09:20.875 --> 00:09:22.970 Now, from a game standpoint, 00:09:22.970 --> 00:09:25.250 any exciting games that you guys have seen 00:09:25.250 --> 00:09:26.440 lately that use some really neat 00:09:26.440 --> 00:09:27.640 services is really neat integration. 00:09:27.640 --> 00:09:29.380 I've heard Fluffy Fairy for example, 00:09:29.380 --> 00:09:30.630 we're going to be interviewing later on 00:09:30.630 --> 00:09:32.010 this week as well and maybe 00:09:32.010 --> 00:09:34.835 talk about some of the services they've used on playFab. 00:09:34.835 --> 00:09:36.860 >> Yeah, that's the one I would have pointed to because 00:09:36.860 --> 00:09:39.370 so the Fluffy Fairy guys are going to be doing 00:09:39.370 --> 00:09:42.680 a talk here at GDC this afternoon specifically about 00:09:42.680 --> 00:09:44.990 their LiveOps strategy that they used for 00:09:44.990 --> 00:09:47.550 their game and how they've developed it. 00:09:47.550 --> 00:09:50.425 And that game was put together in eight weeks. 00:09:50.425 --> 00:09:50.985 >> Eight weeks! 00:09:50.985 --> 00:09:51.635 >> Yeah eight weeks. 00:09:51.635 --> 00:09:53.050 >> That's amazing. 00:09:53.050 --> 00:09:55.200 >> Yeah, I know it's like a game jam right. 00:09:55.200 --> 00:09:59.800 They did a little rapid approach 00:09:59.800 --> 00:10:00.960 to getting the game out to the market, 00:10:00.960 --> 00:10:02.480 put it on iOS and Android and 00:10:02.480 --> 00:10:04.010 then just really organically grew 00:10:04.010 --> 00:10:06.010 their user base and took a lot of feedback from 00:10:06.010 --> 00:10:08.225 the users and developed the game, 00:10:08.225 --> 00:10:09.650 tweaked into with it and 00:10:09.650 --> 00:10:11.475 then introduced their LiveOps program. 00:10:11.475 --> 00:10:13.955 And so as part of this, what they're using us for, 00:10:13.955 --> 00:10:16.415 what they're using PlayFab for specifically 00:10:16.415 --> 00:10:19.410 is the obviously authentication and data systems 00:10:19.410 --> 00:10:21.805 for players being able to have the data that you save 00:10:21.805 --> 00:10:23.610 and you can save the game on one device 00:10:23.610 --> 00:10:25.675 and move to another device and continue the game. 00:10:25.675 --> 00:10:28.845 But also the in-app purchasing, 00:10:28.845 --> 00:10:31.560 the analytics of the data 00:10:31.560 --> 00:10:34.775 coming in for the player using user segmentation. 00:10:34.775 --> 00:10:36.305 All kinds of things, right? 00:10:36.305 --> 00:10:38.180 And it all comes together where they're 00:10:38.180 --> 00:10:40.950 using the fundamental components of the service and 00:10:40.950 --> 00:10:43.000 then also the LiveOps layer in order 00:10:43.000 --> 00:10:45.640 to constantly reengage their players 00:10:45.640 --> 00:10:46.980 and make the game more and more popular. 00:10:46.980 --> 00:10:48.210 And Bill, you'll see a lot of 00:10:48.210 --> 00:10:49.500 details about that today in their talk. 00:10:49.500 --> 00:10:51.670 >> That is it, absolutely amazing. 00:10:51.670 --> 00:10:53.820 Well, that's a lot of services and I 00:10:53.820 --> 00:10:55.860 think how easy that it makes it for development right? 00:10:55.860 --> 00:10:58.270 Again, having developed things over the years, 00:10:58.270 --> 00:11:00.550 as developers we like to create things but 00:11:00.550 --> 00:11:01.520 sometimes if it already 00:11:01.520 --> 00:11:02.750 exists it makes sense to use it right? 00:11:02.750 --> 00:11:04.580 Things that have been tested and develop and so, 00:11:04.580 --> 00:11:06.020 the fact that we can take these services 00:11:06.020 --> 00:11:07.810 integrate it and make it easy is amazing. 00:11:07.810 --> 00:11:09.290 How do we developers get started? 00:11:09.290 --> 00:11:10.580 >> How they get started. 00:11:10.580 --> 00:11:10.780 >> Yup. 00:11:10.780 --> 00:11:12.335 >> It's easy. They can just come to 00:11:12.335 --> 00:11:15.700 developer.playFab.com, create an account. 00:11:15.700 --> 00:11:17.980 Automatically that means they've got a studio, 00:11:17.980 --> 00:11:20.025 they can create titles, they can start development. 00:11:20.025 --> 00:11:22.320 I'll be honest, when you first create 00:11:22.320 --> 00:11:24.930 a title you're in our free tee automatically. 00:11:24.930 --> 00:11:26.930 We've actually had people who create 00:11:26.930 --> 00:11:28.580 their games and then 00:11:28.580 --> 00:11:30.570 get them out to market and they start having customers, 00:11:30.570 --> 00:11:32.600 their games are live and we didn't even 00:11:32.600 --> 00:11:34.780 know they were there because they'd never spoke to us, 00:11:34.780 --> 00:11:35.940 they never posted anything 00:11:35.940 --> 00:11:37.450 to our forums asking for any help. 00:11:37.450 --> 00:11:39.230 They just got their game out there and running. 00:11:39.230 --> 00:11:39.680 >> Wow. 00:11:39.680 --> 00:11:41.985 >> So, yeah that's a fantastic. 00:11:41.985 --> 00:11:44.400 >> So, Overnight Booth there's 00:11:44.400 --> 00:11:46.580 this actually two things you guys have over here right? 00:11:46.580 --> 00:11:49.250 The PlayFab definitive guide to LiveOps. 00:11:49.250 --> 00:11:50.600 So, if you happen to be at GDC, 00:11:50.600 --> 00:11:52.235 come and by, check this out. 00:11:52.235 --> 00:11:54.590 Brendan I'm going to ask you in closing here and it might 00:11:54.590 --> 00:11:57.010 be trying to choose the favorite amongst your children. 00:11:57.010 --> 00:11:58.780 Do you have any favorite, 00:11:58.780 --> 00:12:00.540 a favorite service or favorite services? 00:12:00.540 --> 00:12:03.270 >> I'm going to have to go with play stream because 00:12:03.270 --> 00:12:08.520 the play stream is the thing that powers the most. 00:12:08.520 --> 00:12:11.295 To me, what's the most exciting technology that we have? 00:12:11.295 --> 00:12:12.935 The thing that drives all the LiveOps, 00:12:12.935 --> 00:12:14.850 is all these events and being able 00:12:14.850 --> 00:12:16.645 to hook into it and do everything with it. 00:12:16.645 --> 00:12:18.640 You can set up rules where if an event 00:12:18.640 --> 00:12:19.810 comes in and it's got certain 00:12:19.810 --> 00:12:20.980 parameters you fire things [inaudible]. 00:12:20.980 --> 00:12:22.585 >> When kind of event when you say event? 00:12:22.585 --> 00:12:23.130 >> I'm sorry. 00:12:23.130 --> 00:12:24.520 >> When you say event, what kind of event? 00:12:24.520 --> 00:12:26.255 >> Oh it's anything that happens in the game. 00:12:26.255 --> 00:12:29.740 So, when you look at all of our core technology, 00:12:29.740 --> 00:12:31.725 log ins and purchases and things like that, 00:12:31.725 --> 00:12:33.210 all of those things automatically 00:12:33.210 --> 00:12:35.360 generate events into the place stream. 00:12:35.360 --> 00:12:36.865 And it's got all the data about it. 00:12:36.865 --> 00:12:38.465 So, log in event for example, 00:12:38.465 --> 00:12:39.640 has the IP address, 00:12:39.640 --> 00:12:42.055 it has Geolocation of the user, 00:12:42.055 --> 00:12:45.825 and you can use all that to then, again like I said, 00:12:45.825 --> 00:12:48.045 drive user segmentation or 00:12:48.045 --> 00:12:50.790 any kind of rule system that you want to set up to it. 00:12:50.790 --> 00:12:52.730 It's really that's the thing. It's wide 00:12:52.730 --> 00:12:54.350 open to however you want to use it. 00:12:54.350 --> 00:12:56.190 So, in some ways it's like we have a lot of 00:12:56.190 --> 00:12:58.680 best practices in the LiveOps book and a lot of things 00:12:58.680 --> 00:13:02.010 we advise people to do and we like to see people use it 00:13:02.010 --> 00:13:04.080 because they're proven techniques that 00:13:04.080 --> 00:13:06.170 help to make your games more successful. 00:13:06.170 --> 00:13:09.320 But also, I don't want to limit 00:13:09.320 --> 00:13:13.790 people because it's Greenfield, 00:13:13.790 --> 00:13:15.130 you can do whatever you want with this time. 00:13:15.130 --> 00:13:16.720 I want to see the kinds of 00:13:16.720 --> 00:13:17.710 interesting things that people are 00:13:17.710 --> 00:13:18.780 going to use this technology 00:13:18.780 --> 00:13:21.035 to do that I didn't even think of because that's 00:13:21.035 --> 00:13:22.630 part of what really excites me about 00:13:22.630 --> 00:13:23.730 being in this industry in general. 00:13:23.730 --> 00:13:25.400 >> I didn't think of that scenario. That's amazing. 00:13:25.400 --> 00:13:27.110 Now, is this available 00:13:27.110 --> 00:13:28.985 online as well or do you have stop by here to get it? 00:13:28.985 --> 00:13:30.980 >> That will be available after GDC. 00:13:30.980 --> 00:13:33.075 We didn't want to steal our own thunder. 00:13:33.075 --> 00:13:34.695 So, we're giving out here at GDC so 00:13:34.695 --> 00:13:36.620 folks here will be the first ones to get a hold of it, 00:13:36.620 --> 00:13:37.690 have a grip to it. 00:13:37.690 --> 00:13:39.845 Starting next week are going to be sending it out. 00:13:39.845 --> 00:13:42.765 We've invited people through our newsletter, 00:13:42.765 --> 00:13:44.355 to write to us and let us know 00:13:44.355 --> 00:13:46.330 if you guys want to get a copy of it, 00:13:46.330 --> 00:13:50.720 you could write us at devrel@playFab.com 00:13:50.720 --> 00:13:52.515 and just let us know you want a copy of it. 00:13:52.515 --> 00:13:54.610 We'll send out e-copies next week and we'll be making it 00:13:54.610 --> 00:13:56.815 available on our site not long after that as well. 00:13:56.815 --> 00:13:58.330 >> Awesome. Well, Brendan 00:13:58.330 --> 00:13:59.840 this has been super exciting and thank you very 00:13:59.840 --> 00:14:01.360 much for joining us and I'll be 00:14:01.360 --> 00:14:02.680 excited to see what you guys have going forward. 00:14:02.680 --> 00:14:03.280 Thank you very much. 00:14:03.280 --> 00:14:05.170 >> Fantastic. Thank you.