Impact of Technology - Collaborating Online Respectfully

Gaining support for a cause

Networks: from semaphores to the Internet

Spreadsheets

Programming essentials in Scratch: part I

Programming essentials in Scratch: part II

Design Vector Graphics

Computing systems

Development for the Web

Representations: from clay to silicon

Mobile app development

Intro to Python programming

Animations

Data Science

Cybersecurity

Representations: going audiovisual

Python programming with sequences of data

Physical Computing Programming

Computing

Y8 Computing

Key Stage 3

Year 8

UNIT

In this lesson, we will be introduced to the purpose of the unit: to create a mobile app. Over the next two lessons we will develop our first app together "Tappy Tap App" and start by decomposing the problem, using success criteria to help us do this.

App for that

In this lesson, we will be introduced to the concept of event-driven programming and applying this paradigm to the app that we started to develop in the previous lesson.

Tappy tap app

In this lesson, we will complete our Tappy Tap App by making the score screen.  After this, we will then be given a choice of projects to work on to start building our own apps.

School lab studios

In this lesson, we will explore how user input is captured. We will then start to develop our own apps by decomposing the task into more managable steps.

User input

﻿Hello, and welcome to Lesson Four of our Mobile App Development unit. I'm Ben and in this lesson, you're going to continue, with the mobile app development project, that you picked in Lesson Three. We're also going to look at, how we might handle user input. Okay, so all you'll need this lesson is your computer, a web browser, you'll also need access to CODE.ORG. So if you're under 13 and you haven't got an account, please ask your parent or care to sign you up with account or login with their credentials. Okay. So they're not including any distractions that you might have. And if you got a nice quiet place to work that would be absolutely brilliant. Okay, so when you're ready, let's get started. Okay, so this lesson, we're going to look at User Inputs in our Applied Programming Environment. We're also going to look at Decomposition and use that decomposition mindset of skill to break down your app projects into more manageable steps. Okay. And then hopefully once, get started with your app development, you're going to look at including some variables in your project. Okay, so let's get started and look at some user input. Okay. So user inputs. Now it's common for software applications to obtain data from the user. Okay. So I'd like to look at this login window, and I'm sure you've all seen a login window before. Okay. So I'd like to explore this example that you can see on the right hand side and think what data is being collected. How is it being collected and at what point does a user submit the data. Okay, so can you pause the video, think about the three questions and then unpause when you have an answer. Okay, so hopefully you've got an answer now. So let's go and have a look. Okay, so what we have here, you can see the username and password. Now that's where the user would enter in data, probably using a keyboard or some kind of touchscreen keyboard there okay. Now, we will describe those as being TextBoxes because they allow for the user to input a Text String. And what that means is? they're able to put in any combination of letters, symbols and numbers okay that are on the keyboard okay. And obviously that would be natural for username and password because the username password can be any combination of letters, numbers and symbols okay. Then you might have noticed that, we have the things where it says or okay. That's capturing data from the user and the users inputting their choice on that. Now there is what we call "checkboxes" coz they allow the user to indicate, a yes or no response okay. So um you can see if they're left blank that means no. But if they're selected or checked then that means also you might see a "tick" there or "cross" or something that means a user's indicating a yes response. Okay. Then one of the questions is how is the data captured?,ok Now you can see the login button. Now, that is linked to an event now we discussed events, particularly in lesson two and three at this unit. Where we talked about the fact that would then trigger some code. Okay, so that event once we click on the login button, triggers an event that will capture the data that's been inputted by the user okay. And therefore it can be processed however we code it to be processed. So, let's have a look at that okay. Now inside our App Loving Environment, we have this get text okay and in brackets it says . Now get text is a built in subroutine that collected text entered into a text box okay. Now to be replaced with the name given to the textbox. So if you remember when we built our Tappy Tap app sorry, then every time we made a textbox or label we gave it a name, so on okay?. So that's on the drop down where it says get text wherever you want to get text from, we will select that from the Select Change the "id" to the text box where we going to get text from, okay? And also you can see bar x now the x will be replaced with the variable name. So you can use an event handler to determine when to collect the data and what to do with it. Once it has been be collected and linked with the variable. So you can see the example here that we've got on the right hand side. That say, all event login. Okay, so I've created an event. And there's going to be login. So the "id" is on the call login, which might be linked to a button. And then once that event has been triggered, we have a variable called username. That's going to be linked to the get text and then link the "id" username. So you'd imagine in this example, there would be a textbox called "username". And therefore when the login button is being clicked, whatever text is in that username textbox is going to be stored against the username variable username, sorry. Okay. Hopefully that makes sense. So what I'd like you to do is, put into practise in a different context. Okay, so we have a theme park ticket up. Now the purpose of this office app, is to allow the user to enter the number adult and child tickets required. Now once the user selects the submit button and you can see on the image. You can see all the different names of the boxes. So we got a submit button, we got an adult text input, we got child text input, we got results label okay. So once a user selects that Submit button, the data will be captured and process and the total, we explained it in the results label okay. So now we know all of that. So basically, it's going to collect the data from the text boxes. Once we click Submit, it's going to hopefully do some calculation and then it's going to put the results in the results label. So I've got something called. A Parsons problem for you. Okay, our parsing problem is where you're given the lines of code needed to solve the problem, but they're all jumbled up in the wrong order. So what you have to do is you have to put them in the correct order. Okay, so I'd like you to head over to your worksheet now. Okay, so let me just pop up that side. I've had time to task one on your worksheet and re-order the blocks of code to form a working segment to code. Now new worksheets if you can't remember it describes what you need to achieve. When next slide interactively. Then you can drag and drop the lines of code into the correct order. Okay, so once you're confident you've got the correct order unpause the video and we'll go through the solution. Okay, so how did you get on with that? Hopefully you've got a working working segment the code, there's only one way we can find out if you got to correct. And that's to check the answers. Okay, so here's the solution now. So what we already had in places is on event block, which was linked to a submit button. So once that Submit button was clicked, what do we want to happen? Well, we wanted it to get the adult uhm, get the adult text input and get the child text inputs. Okay, now that did a calculation as you can see, so let's see, what happens is we've got a variable called Adult and it's going to get the text from Adult text box and times that value by 12. And stored up against the variable called Adult. Now, it didn't really matter , which order you did this in so if you did uhm, if you had bar child bar adult the other way around, then That would also be in Okay. Okay. But what's important is bar total can underneath that, because what that did, it took the value being held by the variable adult, it also took the value held by the variable child and it adds them together, okay? And it stores them under a new variable called Total. Okay, so that didn't need to be on the third line. And then the fourth line is very important that this was the last one which set text result label to Total. Okay. So once I click the submit button, there's a calculation done to work out the adult to child. And then there's a total variable that add those two values together and then we're showing them to the user in the results label using the variable total. Okay. So hopefully you got the answer to that. Now, let's go back to the project that you wanted to design yourself okay. So you were given a choice in lesson three of those four different types of apps and you picked one so hopefully you got your project diary and you've got your hand drawn designs and you've also designed some success criteria. Okay. But next time to decompose our problem, we don't want to get coding straightaway. Okay, we want to decompose our problem. Now we have done decomposition before in this unit. So let's just give ourselves a reminder about what decomposition is?. So Decomposition is, breaking a problem down into more manageable chunks. Now, as we talked about the beginning of the Tappy Tap app, programming an app for mobile devices is a really daunting task for anybody to undertake. Not just them, not just school aged children or pupils or students for secondary school okay, Okay. That would be a daunting task for anybody. So decomposition helps us break down these umh a larger problem into these more manageable chunks, and therefore making the task less daunting and more achievable. Okay. So that's give you a reminder of how I went about decomposing the tappy Tap app. Now when we decompose it, we had our success criteria, we use that to help us decompose the problem because we could then from the success criteria under description, work out what we needed to achieve. Now we did two levels of decomposition, we did more of a step one, which is a higher level decomposition, where we took, we took the large problem of making our Tappy tap app game and then breaking it down into maybe more manageable chunks. But on a high level, so what I mean by that is I know I need to create screens. For that first step. I know I needed a welcome screen, I also needed a gameplay and they also needed to do a song with the results screen. So that was my more high level decomposition. So straightaway, I've taken this task and still categorised it into these four steps. Now, I put it into four steps when you did it, you might have done it to three steps, you might have done it the five steps, there's no kind of rule on how many steps you need to decompose the problem into it very much depends on what you're trying to solve. So really, I would say for your projects, maybe four or five, but really is whatever you feel comfortable with. Okay, so that's my more high level task to do. Now, designing all the screens. Well, let's say gameplay let's use gameplay as an example. Gameplay in itself again, there's a lot to achieve in gameplay. So gameplay needs decomposing further. And you can see examples where I've done some decomposition, for example screens. So screen was a step and i decompose up further by creating a by saying, right, I need to create screens. So how am I going to do that? Well, I need to create three empty screen. So work with give each one an appropriate name. And then my next decompose step, is welcome screen. Again, there's lots of things to achieve with my welcome screen. So I'll decompose it further. So once it gets my welcome screen, I need to design the welcome screen. So the graphical user interface elements to it. So adding images, labels and buttons. So that was the graphical user interface part, but they also needed to code it. So they had a button that when it clicked on the button, it moves to the game screen. So this is just an example and of how I have decomposed it. So I've taken more of a higher level, where I've maybe made three or four or five steps, and then free from the steps, have decomposed it further. I'm making a question have extra steps to help remind me and work through each of these steps. uhm, you know in turn, maybe make a little to do list a checklist of things that we need to achieve. Okay? But either way, rather than having this larger problem, I've now got a smaller problem, I can tackle each one in turn, and just deal with one thing at a time. Okay, so what I'd like you to do now is I would like you to pause the video and like to head over to your project diary not your worksheet, go to your project entirely that you saved in lesson three. And I would like you to go to the decomposition slide, and then decompose your problem. So do some high level decomposition, but do some little further decomposition where you take it down into smaller chunks that you can tackle in turn. Ok. Use your success criteria. You can use your project description well to help you with this. Okay, and remember it there really is no right or wrong answer to this, just break down this problem and make it more achievable for you. Okay, so good luck with that, have fun with it. And once you've decomposed it, then you can unpause the video, and we'll continue. Right So, we've done an awful lot of work already without doing any coding whatsoever. So you've got your success criteria, you've got your hands on designs, now you decompose the problem. So really, it's time for us to get going. Okay? So it is time for you to develop your app. So like, it says on the screen, now that you have decompose the problem, and you have designed some screens, you're ready to start developing. So your steps are, I would like you to sign into code.org, So remember, if you don't have an account ask your parents or care to sign you in. Okay, so get your credentials, username and password, I'd like to start a new project. So far, we've been working with some projects that have been created for you. So you need to go through the step of creating a new project. So select projects, and then click on App Lab. There's straightaway in the top left hand side, I'd like to there's the option to rename your projects do that straightaway Okay. And I'd like to rename the same name as your app title Okay? That's the first step that I will like to do. So uhm all I like to do is so, start the project. And then after that it is just a case of you working through your decomposed steps. Now, I would really like you to enjoy this. And coz this is your app, and you can completely make it your own. you've got some design briefs to meet sorry, this is your app. So do make it uniquely yours okay?. Now, there should be nothing here, that really takes you too much by surprise, or something that we haven't yet done. Okay? So don't be afraid to go back, to what you achieved in Lesson One, two, and three and really open this project and look at the code that you wrote. And that will really help you. Now we've also got some videos and lesson two and three that you might want to revisit to see how we did certain things. But if you're not feeling comfortable with that yet, don't be afraid just in this lesson to really focus on maybe just creating the graphical user interface elements to your app. Okay, now is a rough guide, I'd recommend that you spend around 20 minutes on this, but Some that's just a rough guide to what you Feel comfortable in. And this is lesson four. We're going to be continuing with this in lesson five. And we're also going to be continuing with with it for a bit of lesson six as well. So you don't need to finish it up in this lesson. Okay, the 20 minutes is probably a good guide. So if you pause the video now, start your project and have worked through your decomposed steps and have fun. Okay, so pause the video and I'll see when you when you spend 20 minutes on it. Okay, so we achieved that well done, you spent for around 20 minutes on that app. And hopefully by now as a minimum, you've got a welcome screen or home screen, and you created some of the design elements to that. So you might have a title or label an image of Boston. So if you've managed that, that's a really two thumbs up from me. Okay. Now, what I'd like to finish off this lesson is to go to the your new project diary, and go to your milestone one slide. Okay, Now at this stage, it's really important that you document what you've done. Now you'd be surprised about how much you forget even in one or two days time about what you achieve. In this lesson, so it's really helpful in this lesson for your future self to document what you've done. So I'd like to add a screenshot of your code or design window it doesn't need to be both, um whichever one you think is going to be most helpful to you next lesson. I'd like to write a few sentences just describing what you've achieved in this lesson, and maybe describe any problems that you have to overcome. Because if you've overcome some problems, you don't want spend a bit of time next lesson, having the same problem and work and trying re-work out how you solved it. document how you solved it, and that'll help you remember in future lesson, and how to avoid the mistake or how to correct it, if you if you do make that mistake again. Okay?. And then finally, again, write a note to your future self, write down what you need to focus your attention on in next lesson. So it may well be that you finished this section so you think it would make sense if you did this bit next. Okay, so document that. Because next lesson, we'll spend a little bit time, looking back at this milestone document and making a plan for what you're going to achieve in that lesson. Okay?So again, can you head over to your project diary, so not your worksheet, go to your project diary, find that your master in one slide, and then see if you can write down a few sentences about what you've achieved. Okay? so pause the video and then unpause when you're done. Right, that's all for this lesson. And hopefully you feel a really nice sense of achievement that you got started on your app. So it's not just case planning anymore. we've rolled our sleeves up, and now we're actually designing your own app. Okay Now if you remember, in last lesson, we were able to share your Tappy Tap app . So if if you want to ask, please ask your parent or care if you want to do that. We would love to see your app. We'd also love to see the design what you've done and what stages you're in how did you decompose that problem? So if you'd like to share all that with us, please ask your parents or care to share your work on Instagram, Facebook or Twitter and tagging @oaknational and using the #LearnwithOak. So next lesson, We will continue developing your app. We'll continue working through your decomposed steps as well. Okay, so I'm looking forward to it and i hope you are too, and I'll see you next time.

In this lesson, we will spend time developing our apps further. We will use our decomposed steps and success criteria to help continue with this project.

App development

﻿Welcome to lesson five of our mobile app development unit. I'm Ben and in this lesson, you're going to continue working on the app that you started last lesson, and hopefully make it a little bit more complete. So all you'll need for this lesson is your computer and a web browser. You'll also need access to your project, which is on code.org. So you need to log into your account and if you're under 13, please ask your parents or carer to login to the account for you, okay. So if you can clear away any distractions that you might have, so turn your mobile phone off, although you might want to use it later on to preview your app. And if you can find a nice quiet place to work, that would also be fantastic, okay. So when you've done all of that and you're ready, let's get started. Okay, so in this lesson, we're going to add some user input into our block-based programming language, squish this course, App Lab, to include sequencing and selection. Now last lesson, we looked at user input. So this time we're looking at more, the new thing here is selection, okay. You're going to work through your decomposed steps that you broke down to make the app from the challenge more manageable. So you going to continue working through your decomposed steps and also hopefully you're going to include some variables in your project as well. So let's have a look at that new section that's been added in here, which is selection. Now you might be familiar with selection from other programming units that you might have tackled in the past. Okay? So hopefully some of this, even though you might, well, even though you might not have used selection inside App Lab, hopefully you've used it before somewhere. Whether or not that be in Scratch, or if you've done a Python Programming unit, for example. So this, the block's attack team and the wording might not be too unfamiliar, but let's work through it anyway. So these two blocks of code have the same purpose, which is to provide feedback for the user at the end of a game. So what I'd like to do is pause the video. See if you can read through both blocks of texts and work out, what would the output be if the user scored seven? Okay, and what's the difference between the block of code labelled under number one and the block of code labelled under number Okay, so pause the video, work through the code to see if you can read it and trace through it using, imagine that the score variable is currently stored a seven, okay. So pause the video, have a go at that. And then unpause, when you think you've got some answers. Okay, so how do you get on with that? So let's go through the first one. So it says, if score is greater than 10, now we said score's a variable and the value being stored against score is seven, okay. Now we've got an operator there, which is the greater than, okay. So we're saying if the score is, or seven is greater than 10 or score is greater than 10, if that is true. So we need to work out whether or not that statement is evaluated to true or false, okay. Now, if the statement evaluates to true, it would say, set the text feedback label to great work. So it would say great work. If evaluated to false though, it would output hard luck. Okay. So the question is, is does it evaluate to true or false? Okay, well, so we're essentially asking is seven greater than 10? Well, seven isn't greater than 10. So that evaluates as false. So if it evaluates as false, what's the output going to be? That's right, hopefully you said it's going to be hard luck. Okay, so because the else is triggered therefore it's going to say hard luck. So let's have a look at the second block of code. So the first one are our conditions. So if score is greater than 10. So it's the same condition. So if that evaluates to true then it's going to say great work. Now, if it evaluates to true, it's a false, sorry. We've got another condition that we need to evaluate. So we've got this thing called else if here, okay. So it says else if, so that's the same as saying otherwise really. So otherwise, if score is greater than six, if that evaluates to true, then say not bad, but if it values to false, say hard luck. Okay, so we've got two conditions there in the same selection block. So we've gone from the first one having an if and just a single else. And the second one has an if, then an else if and then an else, okay. So the second one's slightly trickier, but let's go through it in order then. So remember score is the same, seven or stored at a seven. So if score is greater than 10, so is seven greater than 10? Again, that's evaluating to false. So what's the output going to be? Is it going to say great work? No, it's not 'cause it would only say great work if it evaluated to true. So then we ask the next question. Else if score is greater than six. So is seven greater than six? Well, it is greater than six, so that evaluates to true therefore the output will be, not bad. Okay, 'cause the else won't be carried out. Okay, so the else isn't always carried out. It only carries out if that condition, initial condition, works out to be false, okay. And the second one, because we've got an else if, we've got a true, so it looks at the true and if it's false it then asks a further question to be evaluated. Okay, great. Okay, so well done. So let's move on. What I'd like you to do now we've looked at selection is think wouldn't it be great if we could include selection in our app project, okay. So I'd like you to just think, about this for a moment. To think, where could you use selection inside your project? Is there were an opportunity at any point to get feedback, or is there other opportunities where we could use selection to break away from that sequence that's going to take place. Okay. It might be somewhere around user input. Anyway. So let's move on with our project. Now, if you remember the end of lesson four, what I said, is it's really important that you created or completed your Milestone 1 slide. And the whole point of that was, you were talking to your future self about what you achieved last lesson, what you think you should be achieving in this lesson, okay. So now you need to listen to your past self and look at what you said you were going to achieve, so you can make a plan. So I'd like you to think big and work out what your plan is for this lesson, okay. So I'd like you to, first of all, go ahead and open your project on code.org that you started last lesson. I'd also like to open up your project diary and look at that Milestone 1 slide. And there, from that point onward, you should be able to read what you achieved last lesson and what you said, you're going to achieve this lesson, okay. So try and come up with a plan of what you think you could achieve in this lesson. Now it might help you to think that you probably, I would recommend around 40 minutes work on this in this lesson. So when you're making that plan, think I've got about 40 minutes worth of time to work on this, okay. So see if you've got a realistic, try and make a realistic plan of what you can achieve, okay. So pause the video, open your app, open your project diary and have a look at your Milestone 1 document. Right, okay. So what I'd like to do now, you've done all of that. You're now ready to get started with your app, okay. Now you started last lesson. So start again this lesson and continue developing it. Now like I just said, you've got about 40 minutes, so let's see what you can achieve. Let's see if you can start working on that code today, get some events in there. Maybe put some variables in there, see if you can slot some selection. But I suppose what's also really important is you look at your decomposed steps and work through those decomposed steps, okay. Don't go into this with a big problem to solve, okay. You've already broken this down into smaller steps. So just work through those more manageable, achievable steps, okay. So have fun with it most importantly. So pause the video, work through it, have fun and then unpause, when you spent around 40 minutes on this project. Okay, so you're joining me now because hopefully you've got further with your project and you've got to a nice point where you think you can stop for this lesson, okay. So that's really well done. And hopefully you've managed to achieve some code in there and you've put some events and maybe some selection, that would be really wonderful. Now what I thought would be a great opportunity now is for us to gain some feedback. Now I know you might be thinking, well, I haven't finished it yet so what's the point in getting feedback now? Well, absolutely, there's always points in getting feedback as often as you can, because it may well be that you've done some things that you think are really great but actually the people who are going to be using your app, maybe they don't think it's quite as great as you thought. Or they might think of nice new features that you could add or things that you could do differently that would make it even better, okay. So what I'd like you to do is think about, how are you going to measure whether or not the app has met the project brief? Well, hopefully you're thinking we've got our success criteria. So that's my starting point. So get the user to get whoever's giving you feedback to look through your success criteria and work out whether or not they think it's being met. Now, if that's an opportunity for you to have somebody maybe where you are now to give you feedback, that would be great. Anybody would do. It could be your mom and dad, your brother, sister. Anybody who thinks, who can look over your app and work through it and see whether or not, see what they think of it basically. So to do this, your app needs to be open and ready to run. So they don't need to see the code. It's fine if they can see the code, but that's not what they're judging, they're judging the user experience, right? So I'd like to also have your project diary open and on the feedback slide. On the feedback slide, the space for you to add your success criteria. So make sure the table's completed with your success criteria and then simply ask anybody to come along and just have a go at your app, whatever state it's in and see if they can give you some really useful feedback, okay. You might want to tell them that it's not finished and so they have that understanding and that's absolutely fine, but any opportunity for feedback is a really good thing. So if you can do all that, pause the video, go and find somebody now to give you some feedback. And then once you've got the feedback and they've noted down their thoughts unpause he video and we'll continue. Okay, so hopefully you've got some feedback by now and you've been able to read over what they said. Do you think it was useful? Hopefully they've given you something to think about that you might even want to plan for now that you can work on in lesson six, okay. So on that note, I'd like you to do exactly what you did at the end of lesson four but this time go to Milestone 2. So what you need to do is, you need to add a screenshot of your code or design window. It doesn't need to be both, just one of them. Write me down a few sentences about what you achieved in this lesson. And again, most importantly, write a note to your future self about what you've got left to achieve in lesson six. So lesson six is our last lesson in this unit. So try and make a plan of realistically what you think you can complete by the end of one more lesson, okay. So again, I would like you to pause the video now, head over to your project diary, find the Milestone 2 slide and fill that in and unpause once you've done that. Okay, so that's all for lesson five. And really, I imagine now your app is starting to take a really great shape and I'm really looking forward to seeing what you've achieved, okay. So if you'd like to share your work, please ask your parents or carers to share your work on Instagram, Facebook, or Twitter, tagging @OakNational and using the #LearnwithOak. I really can't wait to see these projects and hopefully have a go, have the opportunity to have a go myself, okay. So I'm looking forward to seeing you in lesson six, where we'll finish off your projects and complete all this great work that you've been doing, okay. So I'll see you then.

In this lesson, we will complete and evaluate our app development project. Once our apps are complete, we will evaluate their success, both against our own criteria and by answering a short set of questions.

Project completion

﻿Hello, and welcome to Lesson Six in what is our final lesson about Mobile App Development Unit. So, in this lesson, you're going to complete your app and make it the best it can possibly be in the time that we have. So, all you'll need for this lesson is your computer and a web browser, you'll also need your project diary, you'll also need your application that you started in the last two lessons, so you'll need access to your code or account. So, if you're under 13, please ask your parent or carer to log into their account so you can access the work that you've been doing. So, if you can clear away any distractions that you might have, so, turn off your mobile phone and find a nice quiet place to work. And when you've done all of that, let's get started. Okay, so in this lesson, let's mention this, it's all about completing your application. So, it would be really great if we can include as many as those key programming concepts, that we've learned about so far in this unit. Include them inside your application. For example, how can we include some user input inside your application, selection, sequencing and variables? But also I want you to work through those decomposed steps, you've done an awful lot of hard work in the planning. So, follow through that planning, look at your success criteria in the project brief, look at your decomposed steps and work through them in turn. And if you do all of those things, you'll get the app to a really good place by the end of this lesson. Now, hopefully you know by now that I like to start a unit, also a lesson, sorry, with a challenge. So, this challenge is called debug the code. So, as you see on the screen, the following code, which is meant to convert currency between British pounds and Australian dollars, unfortunately is not displaying any value in the australian_label. So, my question to you is, which of the following blocks of code would be most appropriate to help you debug the problem? Okay, so and remember, debugging is trying to find out that error that's happening inside the code. So, look at those four blocks of code and think, which one would help me do that? Now, before you do that, make sure that you read the main block of code, the top right hand side to get a feeling for what the program's doing, and then work out which of those four blocks of code which would solve the problem the best, okay? So, pause the video and unpause when you think you have an answer. Okay, so hopefully you've got an answer for that now. So, let's work through these four blocks of code and see if we can rule out any early on, okay? So, number one says console.log, australian_label in speech marks. Now, first of all, there are two problems that would make me rule that one out, okay? Because, if we were to log, if you remember, we've used console.log before, if you remember when we were doing our tappy top up, we used it when we wanted to show the score incrementing. So, just to prove to ourselves that it was working, we could see the value of that score variable as it was incrementing, okay? So, that's when we used it before. So, if we wanted to log the australian_label, because it's in speech marks, it means that wherever we put this block of code, it would only ever show the words australiam_label which is not what we want. And do we actually want to log what the value of australian_label is? I'm not sure we do it this stage because we already know it's not displaying any value there. So, we probably, that won't be the first thing that we try. Now, I've told you about the fact that the speech marks means that would only ever show whatever's in between the speech marks, and that's not what we want. So, let's rule out number one, and we can also rule out number four too, because that's also in speech marks. So, which one's going to be better for us, number two or number three? So, what do you think? So, see if you can shout out the answer to the screen for me, you think it's number two or number three? So, three, two, one, it is... Number two, okay? We are going to use that console.log, which is a really good one to use. And we're not going to use a speech marks but we do want to log what's happening with conversion, okay? Because setText australian_label to conversion, what we need to know what's going on with conversion, has it done the calculation? Has it collected any data? Did it collect, did it get the text from the pound variable, okay? So, our first port of call with we're trying to solve this problem will be, working out what's going on with that variable conversion. If all that's looking, a bit suspective, we can't find the problem, then go on a step further back and see what's happening with the variable pounds. Is it getting any, and is it getting any value from that text box? You see, we've got getText pounds_text_entry, but we've another thing we can try. But what we're trying to do here, is we're trying to really determine what the problem is, and see if we can work out how to solve our own problems. So, you can use the console.log in your app development, to see if you can solve the problem. So, my other question here is, where would you place this block of code? So, pause the video, we know the console.log is going to be the one that we want. So, where do we put it in this block of code? So, pause the video, see if you can answer. Okay, so, hopefully you got the answer that we would put it just above setText. We can't put it anywhere else because, if we put it above var conversion, that variable has not been created, and nothing is going to be stored against it. So, we try and log conversion before it's either that variables even been initialised, then that won't work, okay? So, the only way or place we can put it is work out what's going on with it before it appears in the text label australian_label, okay? So, that would be a great place to put it. Now, let's go back to your application. So, hopefully, that debugging task is giving you an indication of you, if you come across any problems with your code in this lesson, try and debug your own problems using console.log. But, I'd like to go back and listen to that advice that your former self gave you at the end of lesson five. So, I'd like to think big and work out what your plan is for this lesson. So, to do this, you need to open your project on code.org and get a feeling of where you're up to. I'd like to open your Project Diary and look at your Milestone 2 slide. And that will give you an indication of what you did last lesson and what you think you could have achieved or need to achieve, sorry, in this lesson. Okay, so read over what you achieved, read what you said you're going to achieve, and then unpause this video once you've done that. Okay, so now you've got a sense of what you thought you could achieve in this lesson when you wrote it last lesson. So, hopefully, you now feel inspired to really get the job done, okay? Now, don't be too disappointed. If you don't manage to finish it in this lesson, you can, this application is completely yours, and you can finish it whenever you like. But I would say roughly, we've got about 30 minutes in this lesson to get you up to the best place it possibly can be, okay? So, remember you should be working through your decomposed steps, you've already done your planning, just continue working through those decomposed steps and treat them as a checklist, okay? So, pause the video. And most importantly, please have fun with this last opportunity to get your application finished. So, unpause the video after about half an hour, half an hour's worth of development time. Okay, so how did you get on with that? Now, hopefully, you've finished your app or gotten to a point where you kind of feel really proud of it, okay? Now, I said, don't worry if you haven't finished it, you can only do so much in the time that you've been given. But hopefully, at least as a minimum, you've got an app that you've worked out what your graphical user interface elements are going to be, you've put some coding in there, linked to some events, maybe done all the things or if you've done all of those things, then a big well done, you've done an amazing job, okay? So, the only thing left for us to do now, is to evaluate it, let's judge the success of our project, okay? So, what exactly is meant by evaluation? Well, to evaluate something means to judge or to calculate the quality, importance, amount or value of something. Now, I think there are two really important words there, and they are to judge or calculate. Now, those are different things. So, how can we calculate the quality of our project? And how can we judge the quality of our project? Well, I said they're two different things. Now, if we think about calculation, that's something very factual. Now, what parts of our project so far can we judge? Can we look at the quality? So, can we calculate the quality based on very factual things? Well, that would be our success criteria. Now, this success criteria should only allow for yes/no answers. From that point of view, we can go through our success criteria, give each one a yes or no, and then we can calculate how much of our success criteria we've done. So, the next part is, how can we judge the quality? Well, this is something that is subjective, and it's based on your opinion. So, that's the next step that we got to do, we've got to look through our success criteria, and then also add in our opinion, okay? So, what I'd like to do is, I'd like to head over to your Project Diary, again, I'd like to navigate to the success criteria slides, and fill in the table where you can judge it yourself with a yes/no criteria. Now, that should give you a sense of what you've achieved, and maybe what wasn't achieved, and maybe still could be achieved, and then what I'd like to do, is navigate to the evaluation slide and answer the questions on there. And that's where you can give your thoughts and your opinion. So, if you can pause the video now, and then go over to complete your evaluation, and then unpause when you're done. Okay, for that... So, that's all for this lesson, and it's all for this unit. Now, I really hope you enjoyed that, and I really hope you feel massively proud of what you've achieved. Remember, it doesn't matter if you haven't finished your app. The app is there, and if you want to complete it, or if you want to develop your own different type of application based on what you've learned, we would really love to see that. So, if you feel willing to share your app or any future creations with us, please ask your parents or carer to share your work on Instagram, Facebook, or Twitter, tagging @OakNational and using the #LearnwithOak. So, I'm Ben and that's all from me. And like I say, I hope you enjoyed it, and I hope to see you on some future units. Okay, so, bye.

Unit Overview: Mobile app development

Lessons: