Short answer: a solo developer can keep up one post a day on two or three accounts by batching: one half-day to record and cut, one hour to write captions, and short daily check-ins. Protect coding time by putting all content work on fixed days, and automate the repetitive part (posting at set times), not the creative part.
The weekly plan
Assumptions: two TikTok accounts plus one YouTube channel, one post per account per day, about 4–6 hours of content work a week. Adjust to your pace.
| Day | Content work | Time (assumed) | Posts going out |
|---|---|---|---|
| Monday | Record: 10–15 screen clips and a few talking bits | 2–3 h | Scheduled posts |
| Tuesday | Cut into 14–21 short videos | 1.5–2 h | Scheduled posts |
| Wednesday | Captions, hooks, assign to accounts | 1 h | Scheduled posts |
| Thursday | None (coding day) | 0 | Scheduled posts |
| Friday | Reply to comments, note questions for next week | 30 min | Scheduled posts |
| Saturday | None | 0 | Scheduled posts |
| Sunday | Review numbers, pick next week's angles | 30 min | Scheduled posts |
What a batch looks like
From one recording session you can usually cut:
- 3–4 tutorials ("do X in 3 taps")
- 3–4 problem/solution clips
- 2–3 build-in-public clips (what you shipped, what broke)
- 2–3 slideshows from screenshots
Different edits go to different accounts; don't post the same file everywhere. See UGC video formats and slideshows for apps.
Rules that keep it sustainable
- Fixed days. Content never interrupts a coding day.
- Templates. One caption template, one slide template, one end card.
- A hook bank. Write hooks when you think of them; see hook patterns.
- One metric. Watch link taps or installs per week, not every view count. See metrics.
- Stop what isn't working after a fair test, not after one post.
When the week goes wrong
Releases slip and bugs happen. Keep a buffer of five to seven finished videos that aren't tied to a date (evergreen tutorials work well) so posting continues through a crunch week. If you skip a batch day, cut the posting rate for that week rather than reposting old files on every account.
What to automate
| Task | Automate? | Why |
|---|---|---|
| Recording and editing | Mostly no | It's where the ideas are |
| Captions | Draft with help, edit yourself | Voice matters |
| Posting at set times | Yes | Repetitive, easy to forget |
| Warming new accounts | Optional | Normal browsing is slow manual work |
| Replying to comments | No | Real replies build trust |
| Reporting what posted | Yes | Saves checking each profile |
A solo setup with Farmero
Farmero runs on your Mac and posts from your own iPhones through the real apps, on a manual schedule, a set schedule or smart windows. It reports what posted, what didn't and what was refused on the Mac and optionally to Telegram or ntfy, so you check once a day. The Solo plan covers three iPhones and 24 accounts; the free trial is seven days with no card. Start with the quickstart. Automating these apps may breach their terms, and nobody can promise an account will never be restricted.
FAQ
How often should an indie developer post on TikTok?
Once a day per account is a common target if you can make distinct videos. Consistency matters more than volume.
How much time does it take each week?
With batching, roughly four to six hours for two or three accounts, as an assumption. Your editing speed changes this most.
Should I show my face?
It helps build-in-public content but isn't required. Screen demos and slideshows work without it.
What should I never automate?
Comment replies and the creative decisions. Automate the posting and reporting.