Building a Digital Product From Your Phone

A phone can make and sell a real digital product. The breakage is not in the making; it turns up at export, at checking and at upload, which are the three steps every phone-only tutorial walks past.

Work out which steps need a bigger screen before you start, rather than after you have built something you cannot get out of the app.

Formats that build cleanly on a phone, and the ones that only half do

Cleanly: single-sheet printables made in a phone design app, photo packs, preset files, short audio recorded on the phone itself, a short written guide typed in a documents app, and social templates that were sized for phone screens to begin with.

Half: multi-page layouts where margins and page numbers have to line up across pages. Spreadsheets with formulas, which are editable on a phone and miserable to build there. Anything with precise measurements, since you cannot judge a millimetre on a phone canvas held at arm's length. Long documents, where scrolling costs you more time than typing.

Not at all: video courses, software, anything needing a font installed at system level.

Pick from the first list for a first attempt. Which format to attempt first is a bigger decision than which device you own, but the device narrows the field in a useful way.

The export problem: making a file that opens properly on a desktop

An app's own project file is not a product. If the buyer needs the same app and an account to open what you sold them, you have sold homework. Export to PDF, PNG, JPG, MP3 or a zip, then check the extension on the exported file in a file manager rather than trusting the app's confirmation screen.

Watch the share sheet. On a phone, sharing can produce a cloud link rather than a file, and a link can expire, demand a login, or display your account name to a stranger. Save the export to the device first, then upload the saved file.

Two more phone-specific traps. Fonts that live inside a design app can drop out on another machine unless the export embeds or outlines them, so choose a flat format whenever you are unsure. And zipping a multi-file product needs a file manager app that can create archives, which not all of them can, so confirm yours before you promise a set.

Checking your own work on a device that is not the one you made it on

You cannot judge your own export inside the app that produced it. It will look correct there permanently.

Three checks in order. Open the exported file in a different app on the same phone: a plain PDF viewer, a browser, the file manager preview. Then get it onto a screen you did not build it on, either by sending it to someone who can open it on a laptop and screenshot what they see, or by opening it yourself on a library machine. Then, if it is a printable, print one page at a shop or a library counter before anybody pays for it.

You are looking for substituted fonts, images that lost resolution, margins that shifted, colors that went dull, and pages in the wrong order. Every one of those is invisible on the phone and obvious everywhere else.

Uploading and listing from a phone without the listing looking rushed

The listing is where phone-made products give themselves away. Descriptions typed straight into a marketplace form on a handset come out short, autocorrected, and missing the words buyers search for.

Write the description in a notes app first. Full sentences, file formats listed, page sizes stated, what software opens it, what is and is not included. Read it once more, then paste it in.

For preview images, check the crop on a bigger screen, because marketplace thumbnails crop differently from your phone gallery and heads and headings get cut. Load your own live listing in a browser set to desktop mode and look at it the way a buyer on a laptop will.

Set aside a proper session for uploading instead of doing it in a supermarket queue. Phone upload flows lose form data when a call comes in, and nobody types a good description twice.

Borrowed and public computers, used for the steps that need them

Batch the desktop-only work so a single session covers all of it: the final export check, zipping, bulk uploads, printing a proof.

Libraries have public machines, usually with a time limit and no ability to install software. Community centers, job centers and colleges have them too. Move your files through a cloud account rather than a cable, since you may not be allowed to install a driver.

Then the hygiene. Use a private browsing window, never save a password, sign out of everything including the cloud drive, and delete whatever you downloaded to that machine before you stand up. Assume the browser keeps a history you cannot clear.

If getting to a library is itself the hard part, earning while you have no car is the same planning problem in a different costume: batch the trips, and do everything that needs the place in one visit.

Some products need a desktop and always will

Do not attempt a video course, a piece of software, a long workbook with a contents page, a product where color has to match a print standard, or anything a client will open in professional design software and expect to find layers in.

The pattern behind all of those is precision and duration. A phone is fine for a task with a short session and a forgiving output. It fights you on anything long or exact, and the fight eats hours you would rather spend telling people the product exists.

If the phone is your only device and money has to arrive sooner than a product will bring it, sell your hours instead: freelance work you can do from a phone starts paying on a much shorter clock. And before you buy any app, work through the free tools you can run a business on first, because a paid app earns its money only after the free one has run out of room.