Our other projects
The brief was to create a native iPhone app that converts text into audio while keeping provider credentials out of the app bundle.
A text-to-speech app needs a clean writing and playback experience, but provider keys and billing-sensitive calls should not live directly inside the client app.
Provider availability, billing state, and fallback behavior must be verified before making public claims about cloud voice quality.
SoFlow built a native SwiftUI app pattern with a Cloudflare Worker provider gateway for text-to-speech generation.
The iPhone app owns text entry, history, playback, and sharing. The Cloudflare Worker owns provider calls and protects API keys from the client.
- Native iPhone text-to-audio workflow
- Worker-backed provider boundary
- Playback and sharing flow
- Provider keys kept out of the app
VoiceForge demonstrates SoFlow's ability to combine native app UX with Cloudflare-backed AI provider orchestration.
- Existing Work item points to the public app subdomain
- Provider state should be reverified before a full case study is published
Does the iPhone app call AI providers directly?
The intended architecture keeps provider calls behind a Worker gateway so credentials are not exposed in the app.
Is this a Webflow project?
No. Webflow is only the public story surface. The app runtime is separate.
What should be verified before publishing this as a full case study?
The live provider path, fallback behavior, screenshots, and production app state should be checked before expanding public claims.
This work shows that SoFlow can build app experiences where Webflow tells the story and a separate runtime owns the product logic.
Does the iPhone app call AI providers directly?
The intended architecture keeps provider calls behind a Worker gateway so credentials are not exposed in the app.
Is this a Webflow project?
Heading 1
Heading 2
Heading 3
Heading 4
Heading 5
Heading 6
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.
Block quote
Ordered list
- Item 1
- Item 2
- Item 3
Unordered list
- Item A
- Item B
- Item C
Bold text
Emphasis
Superscript
Subscript
Heading 1
Heading 2
Heading 3
Heading 4
Heading 5
Heading 6
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.
Block quote
Ordered list
- Item 1
- Item 2
- Item 3
Unordered list
- Item A
- Item B
- Item C
Bold text
Emphasis
Superscript
Subscript
Text-to-speech provider calls risked being coupled too closely to the client app.
The app can keep the user experience native while routing provider work through a controlled backend boundary.
This is an app workflow, not a Webflow page. Webflow can explain the app, while SwiftUI and a Worker gateway own the actual product behavior.
