# Rork Max: inspect a browser-built SwiftUI to-do app

Separate the working app, native features and publishing path when evaluating the browser-based development example.

[HTML](https://lukejbyrne.com/library/guides/pqq_yafai9y/)
Content language: en
Author: Luke Byrne
Video published: 2026-02-20
Guide published: 2026-11-02

[Watch the video](https://www.youtube.com/watch?v=pQq_YaFai9Y)
Video language: English

## Begin with one app and its core task

The February demonstration uses Rork Max to create an AI-powered to-do app in a browser. The description presents native SwiftUI development without a Mac or Xcode and names Dynamic Island, widgets and live activities among the supported features discussed. The original product link is https://rork.com/?ref=ailuke.

The app build starts at 0:49 and the AI-fix section at 2:22. Establish what the to-do app should actually let its user do, then inspect the initial result before adding platform-specific extras. The exact starting prompt is not reproduced in the published description.

1. Describe the app’s main user and task-management behaviour.
2. Follow the build example and try the initial app.
3. Use a specific observed problem to guide the correction, then check the changed behaviour.

## Check interface and native features separately

The interface chapter starts at 4:16 and native iOS at 4:45. Inspect how the app presents its tasks before evaluating the platform features. A native-looking screen and a functioning widget or live activity are different outcomes.

The source names Dynamic Island, home-screen widgets and live activities. Check the feature relevant to your version of the app in its actual intended context. Keep the underlying task state consistent with what the feature shows, rather than assessing it only as an attractive extra surface.

1. Review the main interface and its task controls.
2. Follow the native-feature example and inspect its output.
3. Compare the displayed information with the app state it is meant to reflect.

## Follow login and publishing without collapsing the stages

Login begins at 6:09, publishing at 7:07 and the demo at 7:57. The description includes Google login and says Luke ships the app to the App Store from the browser. That is the original account of the workflow; this companion does not independently establish a current public listing or today’s submission requirements.

Inspect the intended login behaviour, then follow the recorded publishing route with the correct project. Compare the final demo with the original to-do-app task. A build, a submission and store availability are separate statuses to keep clear when adapting the example.

## The takeaway

Check the basic app first, then its native features and login, and track the actual publishing status separately.

## Workflow resources

- [rork.com](https://rork.com/?ref=ailuke)
- [ailuke.short.gy](https://ailuke.short.gy/pQq_YaFai9Y1)
- [ailuke.short.gy](https://ailuke.short.gy/pQq_YaFai9Y2)

## Chapters

- [0:00 Roark Max](https://www.youtube.com/watch?v=pQq_YaFai9Y&t=0s)
- [0:49 Build app](https://www.youtube.com/watch?v=pQq_YaFai9Y&t=49s)
- [2:22 AI fix](https://www.youtube.com/watch?v=pQq_YaFai9Y&t=142s)
- [4:16 UI](https://www.youtube.com/watch?v=pQq_YaFai9Y&t=256s)
- [4:45 Native iOS](https://www.youtube.com/watch?v=pQq_YaFai9Y&t=285s)
- [6:09 Login](https://www.youtube.com/watch?v=pQq_YaFai9Y&t=369s)
- [7:07 Publish](https://www.youtube.com/watch?v=pQq_YaFai9Y&t=427s)
- [7:57 Demo](https://www.youtube.com/watch?v=pQq_YaFai9Y&t=477s)

## Sources and limitations

Written companion prepared 2 November 2026 from this exact published video description and its chapter sequence. The full recording was not independently watched or transcribed for this article, and the products and reported results were not retested. Checklists are editorial adaptations of the documented workflow. Model availability, interfaces, prices and offers may have changed since publication; use the retained original resources for current requirements.

[Original video](https://www.youtube.com/watch?v=pQq_YaFai9Y)