ChatGPT apps: inspect what happens between the request and the useful result

Define the job before choosing the integration

The 8 October 2025 video tests newly announced native apps inside ChatGPT. The description lists Canva, Spotify, Coursera, Booking.com, Zillow, Expedia and Figma, then reports connection errors and awkward interface behaviour. This is an early experience review, not a current catalogue or proof that each app is available in every region and account.

1. Choose one clear job, such as finding learning material or exploring a music request, and define what useful completion would look like.
2. Follow the introductory chapters and user-experience friction at 1:03 before treating a launch announcement as a working setup guide.
3. Keep the requested service and intended account identifiable so an unrelated connection does not substitute for the task.

Inspect the connection and the visible app interaction

The chapter route reaches Spotify at 3:35, regional availability and setup at 5:30, and Coursera/Zillow testing at 6:42. A connection step, an embedded interface and a completed user task are different outcomes. The source describes friction that can remove the convenience the integration was meant to provide.

1. Review the actual response to the request and distinguish an app output from ordinary conversational text about the service.
2. Record the first error or confusing interaction and whether the task can continue without leaving the intended workflow.
3. Inspect availability or setup restrictions shown in the recorded attempt rather than assuming the same access across services.
4. Check the final result against the original request; displaying an app panel alone does not establish useful completion.

Separate the interface critique from platform predictions

The video also considers the future of interfaces, the app economy and OpenAI’s direction. Those are Luke’s opinions prompted by an early test, not verified predictions of which business model or interface will win. The description gives no exact reusable setup commands or app-specific prompts, so the recording remains the evidence for the demonstrated interaction.

1. Compare the number of steps and corrections needed with the job you initially wanted done.
2. Keep the observed error separate from any broader conclusion about all conversational apps.
3. Before planning your own workflow, verify current regional access and the specific app’s capabilities independently of this historical launch review.

The takeaway

An app integration is useful when it completes the user’s job with understandable context and fewer obstacles, not merely because it appears inside a chat.