How to learn programming on just a phone

When people set out to learn programming, the first thing that stops them is rarely the syntax. It is the setup: getting a computer, installing an editor, preparing a runtime for the language. You follow the instructions and it still does not work, the error makes no sense, or you are not even sure what you were supposed to install. We have watched plenty of people lose their "I want to try this" right at that step.

Fulfledge does not ask for any of that. Open a lesson in your phone's browser and you can write code, run it, and check your answer, all on that one screen.

What you write here is not simplified, pretend code made just for learning.

• JavaScript runs on the real JavaScript engine already built into your browser
• Python runs as real Python inside the browser
• SQL runs against a real database (SQLite)
• The command-line course boots a real Linux inside your browser

So the error messages you meet here are real too. They are the same ones you will see later on a computer, which means what you learn on your phone carries straight over.

One more thing that matters: the code you write is never sent anywhere. Everything runs inside your own device. Because nothing is shipped off to a server to run, you are not left waiting on the network every time you press Run.

Syntax lessons generally follow these three stages. Integrated practice may omit the basic questions, and knowledge courses use multiple-choice questions instead of coding.

The key is that each lesson covers exactly one idea. The variables lesson is only about variables; the if-statement lesson is only about if statements. Because you are never trying to take in several things at once, you can tell for yourself whether you have got it yet.

You only need to skim the slides. What really sticks is writing it with your own hands afterward. Feeling like you understood the slides and then freezing when it is time to type — that is completely normal. The spot where your hands stop is exactly the spot worth learning.

There are ten practice questions so that you use the same way of writing again and again in slightly different situations. Use the example while you need it, then try with it closed. Learning speed varies, so return to the slides or hints whenever you need them.

Even in the middle of the questions, a button at the bottom of the screen lets you look back at the slides at any time. If you get lost, go back — there is nothing embarrassing about it.

The most tedious part of writing code on a phone is typing symbols. Programming uses a lot of them — ( ) { } [ ] ; " = < — and on a phone keyboard they live on a separate page you have to switch to.

The Fulfledge editor puts the most common symbols in a bar just above the keyboard. Type an opening bracket and its closing partner is added for you, which cuts down the number of taps considerably.

The thing to watch most closely is full-width symbols. If you type symbols while a Japanese or Chinese input mode is on, you can end up with full-width characters like （ or ＝. They look almost identical, but to the computer they are entirely different characters, and your program will error.

• Switch the keyboard to plain English (half-width) when typing symbols
• Only put other scripts inside strings, like "hello"
• If the editor marks a full-width symbol, retype it as half-width right away

The Fulfledge editor flags full-width symbols with a clear marker when it finds them. Early on, a full-width symbol is behind a surprising number of errors, so when you see that marker, suspect it first.

A few more tips:

• Turn off predictive text: suggestions popping up on every English word make it easy to end up with a different word than you meant. Turning off prediction for English input in your keyboard settings makes things much smoother
• Keep the screen upright: the layout is designed so that code and output are easy to compare stacked top to bottom in portrait mode
• An external keyboard works too: connect a Bluetooth keyboard and typing feels almost like a computer. Worth a try if symbols start to wear you out

The biggest advantage of learning on a phone is that you do not need a long block of time at a desk. You can work through a few questions at a time to fit the time you have. How long a whole lesson takes depends on its content and your familiarity with it. A stop or two on the train, the end of a lunch break, a few minutes before bed — each of those becomes study time.

The trick to keeping it up is not deciding in advance how far you will get. Decide "I will finish a lesson today" and on days you are short on time you will hesitate to start at all. Solving just three questions and closing the app is perfectly fine.

• Close a lesson midway and next time it picks up where you left off, half-written code included
• A "continue" card appears on the home screen, so you never need to remember which lesson it was
• The record of the questions you have solved stays inside your own device

We also provide review. Questions you have solved, especially ones you got wrong, come back to the review screen after a day or so. Review lets you check whether you can solve a previous question without the example. If you cannot, read the explanation and try again. Try making a habit of answering a few review questions before moving on to a new lesson.

Everyone learning to program gets stuck somewhere. It is not a matter of talent — it happens to everyone. What matters is knowing how to get out when it happens.

First, read the error message. Fulfledge shows errors exactly as the browser produced them, without rewording them. At first they can look like a jumble, but look closely and they tell you which line went wrong and what went wrong. is not defined, for example, means "nothing with that name was ever created" — almost always a typo in a name.

Next, open the hints. Every question has hints, arranged to bring you a little closer to the answer each time. The first hint is often enough to spark the idea, so try opening them one at a time before looking at the answer.

If you are still stuck, compare your code with the model answer. Your code and the model answer are shown side by side, with only the differences highlighted. Looking at the answer is not losing. If comparing them makes you see "oh, that is where it differed," you have already learned it.

Finally, try it in the playground. It is a free space with no answer checking. Whenever you wonder "what happens if I write it this way," running it there is the fastest way to find out. Deliberately making a mistake to see what error appears is also good practice.

A phone covers a lot of ground, but not everything. To be upfront about it:

• Installing an editor on your own computer and developing while saving files
• Building a large app split across many files
• Publishing an app you made on the internet

Fulfledge is an entry point for picking up how programming thinks and the basic syntax. It is not meant to be where you stop.

As a rough guide, once you have worked through JavaScript (or Python) and HTML & CSS, and finished building the to-do app, you are ready to move to a computer. The to-do app course lets you export what you built in the app as files on your device. Open those files on a computer and you can keep writing in your own editor from there.

Nothing you learned on the phone goes to waste when you move. Variables, if statements, functions, how to read errors — you use all of it exactly the same way on a computer. Only the tools change.