1 00:00:00,080 --> 00:00:03,169 Last time I showed you the Flame device which is our reference device for 2 00:00:03,169 --> 00:00:03,909 developers 3 00:00:03,909 --> 00:00:07,689 and people who want to get to know what a mid-tier device on Firefox OS would look 4 00:00:07,689 --> 00:00:08,148 like. 5 00:00:08,148 --> 00:00:12,240 Once you have your Flame set up it comes like this. By the time the video is out, there 6 00:00:12,240 --> 00:00:15,500 might be a new one so keep up to date, it's really easy to upgrade your 7 00:00:15,500 --> 00:00:16,539 operating system. 8 00:00:16,539 --> 00:00:20,070 To turn this phone into a proper developer phone you just go into settings 9 00:00:20,070 --> 00:00:23,110 and you go into the internet settings 10 00:00:23,110 --> 00:00:27,260 of the phone itself: "device information". Once you're there you click on "more 11 00:00:27,260 --> 00:00:28,080 information" 12 00:00:28,080 --> 00:00:32,769 and then you turn on the developer menu. When you now go back to the main settings 13 00:00:32,769 --> 00:00:36,190 you will get a developer menu that would be confusing for normal end users 14 00:00:36,190 --> 00:00:39,339 but is a real real interesting point for you as a developer. 15 00:00:39,339 --> 00:00:43,499 You have for example the layer borders, you have tile borders, a hardware 16 00:00:43,499 --> 00:00:45,769 composer, the tiling, the over scrolling: 17 00:00:45,769 --> 00:00:49,600 everything that happens in the interface itself to the video card 18 00:00:49,600 --> 00:00:54,069 to the memory can now be inspected by you and that is much much better than 19 00:00:54,069 --> 00:00:57,229 trying to do it over USB and seeing it in the ADB 20 00:00:57,229 --> 00:01:01,510 log but you can do that as well if you wanted to. A very interesting new section 21 00:01:01,510 --> 00:01:04,199 that we have in Firefox OS now is the "developer HUD". 22 00:01:04,199 --> 00:01:09,180 Once you turn that on here and you see it it overlays information onto the 23 00:01:09,180 --> 00:01:10,070 screen for you. 24 00:01:10,070 --> 00:01:13,870 You show the system HUD and all of a sudden you see how much memory is being 25 00:01:13,870 --> 00:01:15,530 used by the system right now 26 00:01:15,530 --> 00:01:19,230 and how much memory is being used by the app that you're currently debugging. 27 00:01:19,230 --> 00:01:23,430 As everything in Firefox OS is an application including the Settings screen 28 00:01:23,430 --> 00:01:26,480 you can actually debug that setting screen while you're using it. 29 00:01:26,480 --> 00:01:30,180 You can also turn on the frames per second which shows you up there how many 30 00:01:30,180 --> 00:01:31,900 frames per second are being used, 31 00:01:31,900 --> 00:01:35,940 the time to load: how long it took to actually load the application that you have 32 00:01:35,940 --> 00:01:36,640 right now, 33 00:01:36,640 --> 00:01:40,840 reflows, yank and all those different settings that you need as a developer. 34 00:01:40,840 --> 00:01:44,870 You see the memory consumption of the app itself and you can cut it down to 35 00:01:44,870 --> 00:01:48,909 like how many JS objects, JS strings and so on have been set for you. 36 00:01:48,909 --> 00:01:52,850 That allows you on the device to see how your app is doing 37 00:01:52,850 --> 00:01:56,640 and for app developers that has been always a pain so we set up this HUD for 38 00:01:56,640 --> 00:01:57,070 you. 39 00:01:57,070 --> 00:02:01,280 Turn it on, test your application, tweak it until it's fast and then bring it to the 40 00:02:01,280 --> 00:02:02,130 marketplace 41 00:02:02,130 --> 00:02:04,370 and other Firefox OS users out there will be happy.