How do I homeschool a kid who only wants to be on the computer?

Stop fighting the device and redirect the pull. The useful divide is consuming versus creating, both of which happen on the same screen. Point the same hours your kid already wants to spend toward building a real thing, and the interest you were fighting becomes the engine of an elective. The homeschool day gives you the flexibility to do this without a bell schedule getting in the way.

Is computer time bad for a homeschooler?

Not by itself. The same hour can be passive consumption or active creation, and those are very different for a developing kid. The honest question is not how long but what they are doing. A kid building a real product on a screen is doing something closer to apprenticeship than to scrolling, even though it looks similar from across the room.

What if my kid only wants to play games or watch videos?

Start where the pull already is. A kid drawn to games or video has the raw ingredients of a maker: they care about how digital things work and look. The move is to channel that into building something of their own, a tool, a site, a small product, so the same energy produces an artifact instead of only consuming one.

Screens and homeschool

The Homeschooled Kid Who Only Wants to Be on the Computer

When the school day happens at home, the kid who only wants to be on the computer is a different kind of standoff. Here is a calmer frame: the screen is not the enemy, the side of it your kid is on is, and the homeschool day is unusually good at flipping it.

By Ibrahim, founder of Wright June 1, 2026 10 min read

Every homeschool parent of a screen-pulled kid knows this standoff, and it is a particular kind of hard when the school day happens at home. There is no bell to end the temptation, no separate building where the device is not. The computer is right there, all day, and your kid would happily spend every hour of the plan on it. You set limits, the limits become a daily negotiation, and you start to wonder if you are losing a battle you did not want to be fighting in the first place.

This is a calmer way to think about it, written for the homeschool day specifically. It does not pretend the pull is not real, and it does not hand you a screen-time chart. It reframes the whole fight, because the frame is where most of the trouble is.

The screen is not the enemy. The side of it is.

The instinct is to treat the computer as the problem and time as the lever: less of it is better, more of it is worse. But that frame quietly miscounts, because it treats two completely different activities as the same thing just because they happen on the same device.

A kid passively consuming, scrolling, watching, half-playing, is doing one thing. A kid actively creating, building a tool, making a site, designing and shipping something of their own, is doing something almost opposite, even though from across the room both look like a kid staring at a screen. One is closer to entertainment. The other is closer to an apprenticeship. Counting them together as screen time is the error underneath the daily fight.

The useful question is never how many hours my kid is on the computer. It is which side of the screen they are on: the consuming side or the creating side. The same device, the same hours, can be either, and that difference matters far more than the number on a timer.

Why the homeschool day is the ideal place to flip it

Here is the advantage you have that a conventional-school parent does not. Your kid's day is yours to shape. There is no fixed schedule forcing the computer into the margins, no separation of school and home that makes building feel like it has to wait until after hours. If your kid wants to be on the computer, you can decide, inside the school day itself, that the computer becomes where a real elective happens.

That means you do not have to win the standoff by force. You can dissolve it by redirection. The same hours your kid is already pulled toward get pointed at building one real thing, and suddenly the activity you were fighting is the engine of their most engaged learning. The pull you could not defeat becomes the fuel you were looking for.

How to channel the pull toward building

The move is not to ban or to bargain. It is to aim. A few principles make the redirection actually take.

Start where the pull already is. A kid drawn to games cares how digital things work. A kid drawn to videos cares how they look and feel. Those are a maker's raw materials. Build from the interest, not against it.
Aim it at a real thing. The shift that matters is from consuming someone else's product to making one of their own, a tool, a site, a small product for a real person. Real and small beats impressive and pretend.
Let it be theirs. The moment building becomes another assignment you hand down, the engagement leaks out. Hold the standard of real, then get out of the way enough that the project stays your kid's.
You hold the bar, not the keyboard. You do not need to be technical to ask what they are making and whether it is real. That is your job, and it is enough.

There is a companion piece in the library on the same idea for any teen, what to do with a teenager who only consumes screens, and a nuanced take on how much screen time is fine if it is creative. Both apply here, with the homeschool day giving you more room to act than a schooled family has.

An honest caveat

Redirecting the pull does not mean every hour becomes productive, and it does not mean limits stop mattering for sleep, movement, and the rest of a balanced day. A kid who only consumes still needs a nudge toward the creating side, and that nudge is real work for a while. The point is that the work is redirection, not a war, and that the device you were fighting can become the most engaged part of the plan.

If you want to see the creating side in action rather than argue your kid toward it, there is a free, real first module at /start that turns what a kid already cares about into the start of a real build, and ends in a brief they write. It is the cleanest way to watch the pull flip toward making.

The honest bottom line

The homeschooled kid who only wants to be on the computer is not best handled by a tighter timer. The real divide is consuming versus creating, both of which happen on the same screen, and the homeschool day is unusually good at flipping a kid from one to the other because you control the day. Channel the pull toward building one real thing, hold the standard without taking over, and the activity you were fighting becomes the engine of an elective. If you want that to be the tech slot specifically, read about the homeschool tech elective that ends in a real product.

Wright is built to point exactly this energy somewhere real: a self-paced program where an 11 to 16 year old turns the time they already want to spend into one real shipped product, with a coach on every step and a short weekly parent check-in. There is a 14 day free trial, card required and cancelable in one click, and your kid keeps everything they built. If the daily computer standoff is yours, you can see whether Wright fits your kid after they try the free module.

From the people who wrote this

Wright is the program that turns all of this into one real shipped thing.

Wright is a 12 module program where an 11 to 16 year old builds and ships one real product: a working thing, live at a domain in their name, with a coach on every step. If you want the structure that comes after the idea, that is what it is for.

If you are not ready to look at a program yet, start with the free Parent Field Guide. It teaches the first move in the founder voice, it is genuinely useful on its own, and there is nothing to buy to use it.

Get the free Parent Field Guide Or see if Wright is a fit for your kid

Or before you decide anything, have your kid do the real first module of Wright, free, no card, tonight: wright.school/start.