Easier to read with cream paper, a tint, more contrast or larger text? Choose your colours and text, once, for every page.

Preview

Choosing development platforms

This is the first page of the lesson. Read it and have a go at the activities. The rest is in the full lesson.

45 minutes

Free tool or paid tool?

Your team will build a school app. You must choose tools. One tool is free and you can change its code. Another costs 20 pounds a month per person and has a support team.

Which is better? It depends. A good developer can explain why. This lesson shows you how.

Key words

WordWhat it meansExample
PlatformA tool or service that developers build on or use for their work.GitHub
RepositoryA store for code and its full history.
BranchingWorking on a copy of the code so the main code stays safe.
BuildTurning source code into a program that can run.
DeploymentPutting the software where users can use it.
ProprietaryOwned by a company. You pay for it and cannot see or change the code.
Open sourceThe code is public. Anyone may read it, use it and often change it.
LicenceThe rules that say how you may use a piece of software.
WorkflowThe steps a team follows to get a change from idea to release.

The cells students fill in are left blank in this preview.

Six stages, six kinds of platform

StageWhat it is forExamples
CodingWriting and fixing codeVisual Studio Code, PyCharm, Visual Studio
RepositoriesStoring code and its historyGitHub, GitLab, Gitea, Bitbucket
BranchingWorking on changes safelyGit, which the repositories above use
BuildingMaking a runnable program, automaticallyGitHub Actions, Jenkins, Maven
TestingChecking the software workspytest, JUnit, Selenium
DeploymentPutting it where users can reach itDocker, Kubernetes, AWS, Azure

The cells students fill in are left blank in this preview.

Proprietary or open source?

Proprietary software belongs to a company. You pay, and you follow its licence. You cannot see the code.

Open source software has public code. Many open source tools are free. You can read the code and often change it. But every open source tool has a licence too, and you must follow it.

Proprietary and open source

ProprietaryOpen source
CostUsually a fee, such as a monthly price per personOften free to use
The codeHiddenPublic
HelpA support team you can callCommunity forums, or paid support from a company
ChangesOnly the owner can change itYou can change it, if the licence allows
ExamplesMicrosoft Visual Studio, JiraGit, Gitea, Linux, Python

The cells students fill in are left blank in this preview.

The choice changes your design

data-callouts.important.label

A tool shapes what you can build. A proprietary service may be hard to leave later. An open source library may have a licence that says you must share your own code. Read the licence before you design.

Quick check

Have a go

Quick check

3 questions
Have a go: your answers are marked here and then forgotten. Sign in if you would like your score kept, and to pick up where you left off.Sign in to keep your score

Your answers are marked here and are not kept. A college account keeps every student’s marks.

Platforms and the workflow

Platforms also decide how the team works together. A workflow is the set of steps for a change: a branch, a review, a test, a release.

Two famous workflows are called gitFlow and GitHub flow. You will try both in the next lesson.

The lesson goes on

5 more parts of this lesson are in the full curriculum, with the tasks, the final check and the labs. A college account gives your students all of it.