Web and mobile: first 30 minutes

You already have a ChatGPT account, or you are about to make one. The first half hour is where people either leave with a usable draft, or bounce between app stores, plan banners, and a half-written prompt that never becomes something you can actually send.

This post continues the series that teaches ChatGPT from scratch. The earlier posts covered what ChatGPT is in plain English, and what Free, Plus, Pro, Business, and Enterprise actually get you without the brochure voice. Here we stay away from desktop modes, Codex installs, Custom GPTs, and API keys. The goal is boring on purpose: open ChatGPT on web or phone, run one real work task with a safe file or paste, rewrite until it is genuinely yours, and leave with a result you can edit and ship.

If you need LLM vocabulary first, read What are LLMs, ChatGPT, generative AI, and more. For vendor-neutral habits around context, verification, and paste safety, the Practical AI series is the companion track. If you also live in Anthropic’s stack, the sibling path is Learn Claude from scratch. All the paths also sit on Learn.

Before you open the tab

ChatGPT is OpenAI’s assistant product. The everyday chat surface for almost everyone is the web app at chatgpt.com. OpenAI also ships official apps for iOS and Android, plus a desktop app for Mac and Windows. The same account can move across all of those surfaces once you sign in with the same login.

For this half hour, pick one primary device. Web on a laptop is the easiest teaching surface, since it gives you a full keyboard, easy file attaching, and an easy copy into email or docs. Mobile is fine for capture and short rewrites once the main draft already exists. Desktop becomes useful later, once you care about Chat, Work, and Codex living in one window, which is a lesson for another post. Day one does not require all three surfaces at once.

Choose one job for the half hour

Vague goals create vague chats. Write a one-line job on paper or in a sticky note before you type anything into ChatGPT:

• “Turn my messy notes into a 400-word project update for stakeholders.”
• “Outline a 20-minute teach-back on weekly revenue for non-analysts.”
• “Rewrite this cold email so it is shorter and less salesy.”
• “Build a study checklist from this PDF chapter,” using text you are actually allowed to use.

If the job needs confidential customer data, payroll numbers, unreleased strategy, or anything you would not put on a shared slide, stop there. Use a redacted sample or made-up numbers instead. Paste discipline gets more room later in this series. For now, day one is for learning the loop, not for stress-testing your company’s data policy.

Where ChatGPT lives: web, mobile, desktop

Think of these surfaces as doors into the same account, not three different products with three different personalities. Features still vary by plan, by device, and by how new a given feature is on each surface.

Sign in with the same account on each surface. Your history generally follows the account, not the laptop, which is why starting on web and polishing on the phone works well when sync behaves itself. If a chat is missing, refresh, confirm you used the same login method, and check that you did not accidentally open a work workspace when you meant a personal one, since Business and Enterprise workspaces can look similar until you notice the org name in the corner.

What you are not installing today

ChatGPT’s product map has grown a lot: ordinary Chat, agentic Work, coding-focused Codex, Custom GPTs, connectors into mail and calendars, and more. Those deserve their own posts later in this series. For this half hour, treat anything that wants a multi-step office agent, a local coding project, or a full connector grant as out of scope. If the interface offers a shiny new product door, close it and stay in ordinary chat.

This matches the same spirit as the Claude track: the first half hour is about one deliverable, not a tour of every label OpenAI has shipped this year. If you already know Claude’s chat-first path, the muscle is the same and only the labels change. See Learn Claude for the sibling product’s version of this lesson.

The first 30 minutes, timed

Use a kitchen timer if that helps you. The point is not speed-running the task. The point is finishing one full loop: account ready, then a real question, safe context, a draft, a rewrite, and a usable file at the end.

Minutes 0 to 5: account and land

1. Open chatgpt.com, or the official mobile app if that is your only device today.
2. Sign in or create the account, preferring a login method you will still control long term (work SSO only if this is a work-approved account).
3. Confirm you can see a new chat and a text box. That is enough interface for day one.
4. Glance at the plan indicators to see whether you are on Free or paid. You do not need to upgrade mid-session; limits exist, and hitting one is not a moral failure.
5. If a model name or mode switcher is visible near the message box, note it once and leave the default in place for this pass, unless your job already requires a specific paid feature.

You do not need a tour of every menu. You need three facts: you are signed in, you can type, and you know roughly which plan you are on, so a rate limit does not feel like the model “broke.”

Minutes 5 to 12: one real question plus safe context

Gather the raw material for your one job. Prefer something short and real over something long and “complete”:

• Bullet notes from a meeting.
• A draft email you hate.
• A public-safe PDF or doc you are allowed to use.
• A screenshot of a slide outline, if the surface accepts images.

On web, use the attach control near the message box when that is faster than pasting a wall of text. Common file types for everyday work include PDF, DOCX, CSV, TXT, and the usual image formats. Limits and supported types change over time, so if an upload fails, shrink the file or paste a slice of it instead. On mobile, prefer short notes or one photo of a whiteboard you own rather than a 40-page PDF you will never skim carefully on a phone screen.

Safe file rule for day one: if the file has customer names, account numbers, unreleased revenue, passwords, or anything covered by your company’s AI policy, do not upload it on a personal Free account. Redact it, invent a toy version, or wait until you know which workspace, personal or company, is actually approved for that data. The skill you are practicing here is the workflow, not the thrill of pasting the real spreadsheet.

Minutes 12 to 22: draft, then rewrite

Paste a structured ask, not a vibe. Here is a template that works for almost any first deliverable:

Role: You are helping me draft for human review, not publishing for me.

Context:
- Audience: [who will read this]
- Goal: [decision or action I want]
- Tone: [plain, short, no hype]
- Constraints: [word limit, no invented stats, flag unknowns]

Source material:
[paste notes or describe the attached file]

Task:
1) Draft the deliverable in the format I asked for.
2) List assumptions you made in bullets.
3) List anything you could not verify from the source.

Refuse:
- Do not invent numbers, quotes, or sources.
- Do not claim the draft is final.

Run it. Read the whole answer once without editing anything yet. Then do a second pass as a human editor:

• Delete anything you would not defend out loud in a meeting.
• Replace vague verbs, such as “optimize,” “enhance,” or “utilize,” with the real action underneath them.
• Check every number against your own notes or file.
• Ask a follow-up only for the broken pieces, such as “Shorten the second section to 80 words and keep my three risks.”

Two or three tight follow-ups beat one giant “make it better” message every time. The rewrite step is the actual product here. The first draft is just clay.

Minutes 22 to 30: export and plant the next habit

Copy the final draft into the place it actually needs to live: email, doc, ticket, slide outline, or an LMS note. Title the ChatGPT chat with the deliverable’s name and today’s date so you can find it again later. If the product offers renaming, use it, because “New chat” is how useful work quietly disappears.

Optional five-minute mobile check: open the iOS or Android app, find the same chat if it synced over, and try one small edit request, such as “make the subject line less corporate.” You are proving the account travels between devices. You are not redoing the whole task on a phone.

Worked example: stakeholder update from messy notes

Suppose your notes look like this. It is a toy example, not a real company dump:

- Q2 pilot: 3 stores, East region
- Dashboard v1 live Tuesday; still missing returns
- Support tickets up ~12% week over week (ops estimate, not finance)
- Next: freeze metric defs Friday with analytics + ops
- Risk: store managers using spreadsheet shadow metrics
- Ask: 2 hours from data eng for returns field in warehouse

A weak first prompt:

Write a project update about the pilot.

That invites invented timelines, fake “success,” and numbers that sound precise simply because language models are drawn to precision theater.

A stronger first prompt, using the template above:

Role: Draft for human review. I will edit before sending.

Audience: VP Retail Ops and analytics lead.
Goal: Clear status, risks, and one ask. No celebration copy.
Tone: Plain. Short paragraphs. No buzzwords.
Constraints: 350-450 words. Do not invent metrics beyond my notes.
If a number is approximate, keep it approximate.

Source notes:
[paste the bullets above]

Task:
1) Draft an email body with subject line options (3).
2) Sections: Status, Risks, Next steps, Ask.
3) Assumptions list.
4) Unknowns list.

Refuse: no invented ROI, no fake quotes from store managers.

What a solid draft should feel like after your edit: the roughly 12% ticket rise stays labeled as an ops estimate, returns stay missing rather than quietly resolved, the ask stays two hours of data eng time, and nothing claims the pilot “drove growth.” If ChatGPT softens a risk into a virtue, put the risk back in. You own the email, not the model.

Web vs mobile for everyday jobs

You do not need a perfect multi-device setup. You need one default and one backup.

A pattern that works for a lot of analysts and ops people: start the real draft on web right after the meeting, then use mobile only for “shorten this” or “give me three subject lines” once the structure already exists. That keeps the heavy context on the surface built to hold it.

Starter prompt pack (copy freely)

Use these as first messages, and replace the bracketed fields. Keep the refuse lines whenever numbers matter.

Meeting notes to update

Turn these notes into a status email for [audience].
Length: [N] words. Sections: status, risks, next steps, ask.
Flag anything that looks like an invented metric.
Notes:
[paste]

Email rewrite

Rewrite this email. Keep my facts. Cut fluff. Tone: [plain / firm / friendly].
Offer 2 subject lines. List any claims that need a human fact-check.
Draft:
[paste]

Explain a concept simply

Explain [topic] for [audience who already knows X but not Y].
Use one concrete workplace example. No hype. End with a 5-bullet checklist
I can use Monday morning.

File-assisted summary

I attached [filename]. Summarize only what is in the file.
Structure: (1) plain summary, (2) open questions, (3) what I should verify
before I act. If the file does not support a claim, say so.

Common mistakes in the first half hour

What “good enough” looks like after 30 minutes

You are done when all of these are true:

• You can open ChatGPT on web or mobile without hunting for the official link or a random third-party app.
• You have one chat that produced a deliverable you would actually edit and send.
• You checked the numbers and claims against your own notes or file.
• The draft lives outside ChatGPT now, in a doc, email, or ticket, not only inside the chat thread.
• You know which shiny doors you deliberately skipped for later, such as desktop modes, Work, Codex, and connectors.

If you only got a pretty first draft and never actually rewrote it, you are not done yet. The rewrite is where ChatGPT becomes a coworker instead of a slot machine.

Questions people ask about the first half hour

Do I need Plus for the first half hour?

Usually not. Free is enough to learn the loop of account, question, safe file, and rewrite. Paid plans raise limits and add more features on top, which an earlier post in this series covered without the hype. Upgrade once you hit real limits, not because a banner looked urgent.

Should I start on desktop?

It is not required. Web teaches the same chat skill just as well. Desktop matters more once you care about Chat, Work, and Codex living in one app, which is a lesson for the next post. If you already installed desktop, just use Chat for this half hour.

Is mobile “real” ChatGPT?

It is. The official iOS and Android apps are first-class surfaces for many people. They are just a weaker place for long documents and careful multi-section edits. Use them for capture and short rewrites, then finish the important work on a larger screen when you can.

How is this different from Learn Claude’s first half hour?

It is the same teaching idea behind different vendor doors and labels. Claude’s first session lands on claude.ai, while ChatGPT’s lands on chatgpt.com. The sibling path is Learn Claude from scratch if you need to learn both stacks for work.

Practice this week

1. Run the timed half hour once with a real, low-risk work artifact.
2. Save your best rewrite as a personal template; a plain notes app is fine for this.
3. Repeat it twice more this week with different job types: one rewrite, one explanation, one file summary.
4. Once ordinary chat starts feeling boring, move on to the desktop app’s modes without abandoning the rewrite habit you just built.

Quick recap

• Land on chatgpt.com or the official mobile apps; the same account can travel between them later.
• Pick one job line before you type anything.
• Follow account, then real question, then safe file or paste, then rewrite, then export.
• Skip Work, Codex, and deep desktop setup until chat itself is useful on autopilot.
• Rename the chat, and own every number before you send it.

Series notes

This is Part 3 of Learn ChatGPT from scratch. The next post, on the desktop app, maps out Chat, Work, and Codex so you stop treating every button like the same chat window. For the Anthropic parallel track, stay oriented with Learn Claude. More paths: Learn hub.

Sources

Product surfaces and download pages change over time. Re-check the official pages when a button moves.

• ChatGPT web app (everyday chat entry at chatgpt.com)
• Download ChatGPT (desktop and mobile download hub)
• ChatGPT on the App Store (official iOS app)
• ChatGPT on Google Play (official Android app)
• OpenAI: ChatGPT for your most ambitious work (desktop Chat, Work, Codex announcement context; details deferred to the next post)
• OpenAI Help Center (account, apps, and plan help articles)
• Analytics Made Simple: Learn Claude from scratch (sibling product path)
• Analytics Made Simple: Practical AI (vendor-neutral verification and workflow habits)
• Analytics Made Simple: Learn (learning hub)

More definitions in Key Terms →

Merch on Etsy

Open store →

Git Version Control Shirt View on Etsy → Standard Deviation White Ceramic Mug View on Etsy → Apache Hadoop T-Shirt View on Etsy → Mean Squared Error Shirt View on Etsy →