Vibecode Dazz Cam
track this build5 steps, step by step0%YES · one-shottable
price $6.99/moyou'd save $83.88/yrbuild time one sittingcategory 📷 photo editingreplaced by 0 people
A film look is a color pipeline: white balance shift, tone curve, channel bias, grain, vignette, bloom. Core Image gives you every one of those primitives on-device, and an agent can wire a live Metal-rendered viewfinder, a camera carousel, and full-resolution capture in one session - this entry's prompt reproduced the core loop as a working iPhone app on the first shot. What you cannot one-shot is a decade of taste: Dazz's dozens of stocks are tuned against thousands of reference photos, and the difference between a filter and a look people recognize is exactly that tuning.
the project pack4 files · fastest path to a working personal build
You are building a lean indie version of Dazz Cam. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== README.md ===== # Dazz Cam indie build ## Goal Build the smallest trustworthy replacement for the core Dazz Cam workflow for one developer or a tiny team. ## Scope A SwiftUI iPhone camera app with a live-filtered Metal viewfinder, a snap carousel of nine film looks including a date-stamped VHS mode, full-resolution filtered capture, import-and-develop for existing photos, and a film roll gallery. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - dozens of hand-tuned film stocks refined over years of color work - the polished video modes - 8mm, camcorder wobble, stabilization - special-effect lenses like fisheye, prism, and starburst done well - ongoing filter drops that chase whatever look TikTok wants this month - one-tap install for friends who will never sideload anything If those capabilities are essential, use GPUImage3 instead of pretending the gap is solved. ===== AGENTS.md ===== # Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs". ===== BUILD_PLAN.md ===== # Build plan ## Original build brief Build me a vintage film camera app like Dazz Cam for iPhone. Requirements: - SwiftUI + AVFoundation + Core Image (Metal-backed), no third-party packages. Full Xcode project from an empty folder: portrait-only, camera + photo-library usage strings in Info.plist. - The viewfinder itself renders through the active film look in real time (30fps+), never a plain preview with an overlay. - Each look is one data struct - temperature, tone curve, channel bias, saturation, grain, vignette, bloom, optional chroma shift - so a new camera is data, not code. Ship nine: neutral, faded 80s negative, instant film, warm Gold 135, gritty B&W, Y2K CCD digicam, neon-violet 3D, expired film, and VHS with a burned-in orange date stamp. - Horizontal snap carousel above the shutter to switch cameras with haptics; shutter press animation, flash toggle, front/back flip. Captures run at full sensor resolution through the same pipeline and land in an in-app film roll. - Import-and-develop: pick any library photo, preview it through every camera, save. Film roll is a grid with Share / Save to Photos / Delete. - On-device only: no accounts, no analytics, no network calls. Handle denied permissions with a Settings shortcut. - README with build steps and how to add a film stock; a unit test proving a fixed image through a fixed stock is deterministic. Build it and fix errors before finishing. - Out of scope: video modes, effect lenses, and Dazz's full stock library - this is nine good looks, not forty. ## Required capabilities - a Mac with Xcode and a physical iPhone - the simulator has no camera - a free Apple Developer account to sideload; 99 USD/year only if you want it on the App Store ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden. ===== .env.example ===== # Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
You are building a lean indie version of Dazz Cam. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== README.md ===== # Dazz Cam indie build ## Goal Build the smallest trustworthy replacement for the core Dazz Cam workflow for one developer or a tiny team. ## Scope A SwiftUI iPhone camera app with a live-filtered Metal viewfinder, a snap carousel of nine film looks including a date-stamped VHS mode, full-resolution filtered capture, import-and-develop for existing photos, and a film roll gallery. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - dozens of hand-tuned film stocks refined over years of color work - the polished video modes - 8mm, camcorder wobble, stabilization - special-effect lenses like fisheye, prism, and starburst done well - ongoing filter drops that chase whatever look TikTok wants this month - one-tap install for friends who will never sideload anything If those capabilities are essential, use GPUImage3 instead of pretending the gap is solved. ===== AGENTS.md ===== # Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs". ===== BUILD_PLAN.md ===== # Build plan ## Original build brief Build me a vintage film camera app like Dazz Cam for iPhone. Requirements: - SwiftUI + AVFoundation + Core Image (Metal-backed), no third-party packages. Full Xcode project from an empty folder: portrait-only, camera + photo-library usage strings in Info.plist. - The viewfinder itself renders through the active film look in real time (30fps+), never a plain preview with an overlay. - Each look is one data struct - temperature, tone curve, channel bias, saturation, grain, vignette, bloom, optional chroma shift - so a new camera is data, not code. Ship nine: neutral, faded 80s negative, instant film, warm Gold 135, gritty B&W, Y2K CCD digicam, neon-violet 3D, expired film, and VHS with a burned-in orange date stamp. - Horizontal snap carousel above the shutter to switch cameras with haptics; shutter press animation, flash toggle, front/back flip. Captures run at full sensor resolution through the same pipeline and land in an in-app film roll. - Import-and-develop: pick any library photo, preview it through every camera, save. Film roll is a grid with Share / Save to Photos / Delete. - On-device only: no accounts, no analytics, no network calls. Handle denied permissions with a Settings shortcut. - README with build steps and how to add a film stock; a unit test proving a fixed image through a fixed stock is deterministic. Build it and fix errors before finishing. - Out of scope: video modes, effect lenses, and Dazz's full stock library - this is nine good looks, not forty. ## Required capabilities - a Mac with Xcode and a physical iPhone - the simulator has no camera - a free Apple Developer account to sideload; 99 USD/year only if you want it on the App Store ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden. ===== .env.example ===== # Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
You are building a production product version of Dazz Cam. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== PRODUCT.md ===== # Dazz Cam product brief ## Problem A film look is a color pipeline: white balance shift, tone curve, channel bias, grain, vignette, bloom. Core Image gives you every one of those primitives on-device, and an agent can wire a live Metal-rendered viewfinder, a camera carousel, and full-resolution capture in one session - this entry's prompt reproduced the core loop as a working iPhone app on the first shot. What you cannot one-shot is a decade of taste: Dazz's dozens of stocks are tuned against thousands of reference photos, and the difference between a filter and a look people recognize is exactly that tuning. ## Product outcome A SwiftUI iPhone camera app with a live-filtered Metal viewfinder, a snap carousel of nine film looks including a date-stamped VHS mode, full-resolution filtered capture, import-and-develop for existing photos, and a film roll gallery. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - a Mac with Xcode and a physical iPhone - the simulator has no camera - a free Apple Developer account to sideload; 99 USD/year only if you want it on the App Store ## Explicit non-goals for v1 - dozens of hand-tuned film stocks refined over years of color work - the polished video modes - 8mm, camcorder wobble, stabilization - special-effect lenses like fisheye, prism, and starburst done well - ongoing filter drops that chase whatever look TikTok wants this month - one-tap install for friends who will never sideload anything ## Success criteria - The primary workflow is measurable end to end. - Setup is reproducible in a clean environment. - Failure, recovery, and support paths are documented. - Product claims match what the implementation actually guarantees. ===== ARCHITECTURE.md ===== # Architecture ## Starting brief Build me a vintage film camera app like Dazz Cam for iPhone. Requirements: - SwiftUI + AVFoundation + Core Image (Metal-backed), no third-party packages. Full Xcode project from an empty folder: portrait-only, camera + photo-library usage strings in Info.plist. - The viewfinder itself renders through the active film look in real time (30fps+), never a plain preview with an overlay. - Each look is one data struct - temperature, tone curve, channel bias, saturation, grain, vignette, bloom, optional chroma shift - so a new camera is data, not code. Ship nine: neutral, faded 80s negative, instant film, warm Gold 135, gritty B&W, Y2K CCD digicam, neon-violet 3D, expired film, and VHS with a burned-in orange date stamp. - Horizontal snap carousel above the shutter to switch cameras with haptics; shutter press animation, flash toggle, front/back flip. Captures run at full sensor resolution through the same pipeline and land in an in-app film roll. - Import-and-develop: pick any library photo, preview it through every camera, save. Film roll is a grid with Share / Save to Photos / Delete. - On-device only: no accounts, no analytics, no network calls. Handle denied permissions with a Settings shortcut. - README with build steps and how to add a film stock; a unit test proving a fixed image through a fixed stock is deterministic. Build it and fix errors before finishing. - Out of scope: video modes, effect lenses, and Dazz's full stock library - this is nine good looks, not forty. ## Boundaries Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors. ## Production baseline - Configuration: validated at startup with safe local defaults where possible. - Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives. - Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions. - Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts. - Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists. - Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test. ## Decision records For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it. ===== AGENTS.md ===== # Agent instructions - Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code. - Implement milestone by milestone; keep each change reviewable and leave the application runnable. - Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present. - Never invent cryptography or silently weaken a requirement to make a test pass. - Use provider interfaces for external services and deterministic fakes in tests. - Add migrations and rollback or recovery notes for persistent data changes. - Log useful operational context without credentials, tokens, passwords, or personal data. - Update documentation and run all checks before completing a milestone. ===== MILESTONES.md ===== # Delivery milestones ## M0 — Decisions and scaffold - Confirm the runtime, persistence model, threat boundaries, and deployment target. - Create a reproducible local environment and continuous checks. ## M1 — Core workflow - Implement the smallest end-to-end product path with validation and tests. - Keep integrations behind interfaces. ## M2 — Trust layer - Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards. - Test abuse cases and destructive operations. ## M3 — Operability - Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration. ## M4 — Release gate - Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise. - Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations. ===== OPERATIONS.md ===== # Operations ## Before release - Validate configuration and secrets at startup. - Define backup, restore, and rollback procedures and test them. - Document logs, error tracking, health signals, and alert ownership. - Set dependency update and vulnerability review expectations. ## Incident checklist 1. Contain the issue without destroying evidence or user data. 2. Record the timeline and affected scope. 3. Rotate exposed secrets and revoke compromised sessions or credentials. 4. Restore from a verified source when needed. 5. Document the root cause, remediation, and regression test. ## Launch constraint Do not market omitted Dazz Cam capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
README.md
# Dazz Cam indie build ## Goal Build the smallest trustworthy replacement for the core Dazz Cam workflow for one developer or a tiny team. ## Scope A SwiftUI iPhone camera app with a live-filtered Metal viewfinder, a snap carousel of nine film looks including a date-stamped VHS mode, full-resolution filtered capture, import-and-develop for existing photos, and a film roll gallery. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - dozens of hand-tuned film stocks refined over years of color work - the polished video modes - 8mm, camcorder wobble, stabilization - special-effect lenses like fisheye, prism, and starburst done well - ongoing filter drops that chase whatever look TikTok wants this month - one-tap install for friends who will never sideload anything If those capabilities are essential, use GPUImage3 instead of pretending the gap is solved.
AGENTS.md
# Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs".
BUILD_PLAN.md
# Build plan ## Original build brief Build me a vintage film camera app like Dazz Cam for iPhone. Requirements: - SwiftUI + AVFoundation + Core Image (Metal-backed), no third-party packages. Full Xcode project from an empty folder: portrait-only, camera + photo-library usage strings in Info.plist. - The viewfinder itself renders through the active film look in real time (30fps+), never a plain preview with an overlay. - Each look is one data struct - temperature, tone curve, channel bias, saturation, grain, vignette, bloom, optional chroma shift - so a new camera is data, not code. Ship nine: neutral, faded 80s negative, instant film, warm Gold 135, gritty B&W, Y2K CCD digicam, neon-violet 3D, expired film, and VHS with a burned-in orange date stamp. - Horizontal snap carousel above the shutter to switch cameras with haptics; shutter press animation, flash toggle, front/back flip. Captures run at full sensor resolution through the same pipeline and land in an in-app film roll. - Import-and-develop: pick any library photo, preview it through every camera, save. Film roll is a grid with Share / Save to Photos / Delete. - On-device only: no accounts, no analytics, no network calls. Handle denied permissions with a Settings shortcut. - README with build steps and how to add a film stock; a unit test proving a fixed image through a fixed stock is deterministic. Build it and fix errors before finishing. - Out of scope: video modes, effect lenses, and Dazz's full stock library - this is nine good looks, not forty. ## Required capabilities - a Mac with Xcode and a physical iPhone - the simulator has no camera - a free Apple Developer account to sideload; 99 USD/year only if you want it on the App Store ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden.
.env.example
# Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
PRODUCT.md
# Dazz Cam product brief ## Problem A film look is a color pipeline: white balance shift, tone curve, channel bias, grain, vignette, bloom. Core Image gives you every one of those primitives on-device, and an agent can wire a live Metal-rendered viewfinder, a camera carousel, and full-resolution capture in one session - this entry's prompt reproduced the core loop as a working iPhone app on the first shot. What you cannot one-shot is a decade of taste: Dazz's dozens of stocks are tuned against thousands of reference photos, and the difference between a filter and a look people recognize is exactly that tuning. ## Product outcome A SwiftUI iPhone camera app with a live-filtered Metal viewfinder, a snap carousel of nine film looks including a date-stamped VHS mode, full-resolution filtered capture, import-and-develop for existing photos, and a film roll gallery. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - a Mac with Xcode and a physical iPhone - the simulator has no camera - a free Apple Developer account to sideload; 99 USD/year only if you want it on the App Store ## Explicit non-goals for v1 - dozens of hand-tuned film stocks refined over years of color work - the polished video modes - 8mm, camcorder wobble, stabilization - special-effect lenses like fisheye, prism, and starburst done well - ongoing filter drops that chase whatever look TikTok wants this month - one-tap install for friends who will never sideload anything ## Success criteria - The primary workflow is measurable end to end. - Setup is reproducible in a clean environment. - Failure, recovery, and support paths are documented. - Product claims match what the implementation actually guarantees.
ARCHITECTURE.md
# Architecture ## Starting brief Build me a vintage film camera app like Dazz Cam for iPhone. Requirements: - SwiftUI + AVFoundation + Core Image (Metal-backed), no third-party packages. Full Xcode project from an empty folder: portrait-only, camera + photo-library usage strings in Info.plist. - The viewfinder itself renders through the active film look in real time (30fps+), never a plain preview with an overlay. - Each look is one data struct - temperature, tone curve, channel bias, saturation, grain, vignette, bloom, optional chroma shift - so a new camera is data, not code. Ship nine: neutral, faded 80s negative, instant film, warm Gold 135, gritty B&W, Y2K CCD digicam, neon-violet 3D, expired film, and VHS with a burned-in orange date stamp. - Horizontal snap carousel above the shutter to switch cameras with haptics; shutter press animation, flash toggle, front/back flip. Captures run at full sensor resolution through the same pipeline and land in an in-app film roll. - Import-and-develop: pick any library photo, preview it through every camera, save. Film roll is a grid with Share / Save to Photos / Delete. - On-device only: no accounts, no analytics, no network calls. Handle denied permissions with a Settings shortcut. - README with build steps and how to add a film stock; a unit test proving a fixed image through a fixed stock is deterministic. Build it and fix errors before finishing. - Out of scope: video modes, effect lenses, and Dazz's full stock library - this is nine good looks, not forty. ## Boundaries Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors. ## Production baseline - Configuration: validated at startup with safe local defaults where possible. - Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives. - Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions. - Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts. - Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists. - Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test. ## Decision records For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it.
AGENTS.md
# Agent instructions - Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code. - Implement milestone by milestone; keep each change reviewable and leave the application runnable. - Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present. - Never invent cryptography or silently weaken a requirement to make a test pass. - Use provider interfaces for external services and deterministic fakes in tests. - Add migrations and rollback or recovery notes for persistent data changes. - Log useful operational context without credentials, tokens, passwords, or personal data. - Update documentation and run all checks before completing a milestone.
MILESTONES.md
# Delivery milestones ## M0 — Decisions and scaffold - Confirm the runtime, persistence model, threat boundaries, and deployment target. - Create a reproducible local environment and continuous checks. ## M1 — Core workflow - Implement the smallest end-to-end product path with validation and tests. - Keep integrations behind interfaces. ## M2 — Trust layer - Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards. - Test abuse cases and destructive operations. ## M3 — Operability - Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration. ## M4 — Release gate - Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise. - Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations.
OPERATIONS.md
# Operations ## Before release - Validate configuration and secrets at startup. - Define backup, restore, and rollback procedures and test them. - Document logs, error tracking, health signals, and alert ownership. - Set dependency update and vulnerability review expectations. ## Incident checklist 1. Contain the issue without destroying evidence or user data. 2. Record the timeline and affected scope. 3. Rotate exposed secrets and revoke compromised sessions or credentials. 4. Restore from a verified source when needed. 5. Document the root cause, remediation, and regression test. ## Launch constraint Do not market omitted Dazz Cam capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
$ choose a build depth, inspect the files, then open the complete pack in your agent
Nobody pays Dazz for AVFoundation. They pay for a curated shelf of looks that are already dialed in - open the app, pick 135 SR, and the photo comes out feeling like 2002 without you touching a slider. That library, and the steady drip of new stocks tuned to current trends, is editorial work a one-shot build does not replicate.
xdozens of hand-tuned film stocks refined over years of color work
xthe polished video modes - 8mm, camcorder wobble, stabilization
xspecial-effect lenses like fisheye, prism, and starburst done well
xongoing filter drops that chase whatever look TikTok wants this month
xone-tap install for friends who will never sideload anything
share on X ↗"I just replaced Dazz Cam ($6.99/mo) with one prompt"
Dazz Cam pricing
dazz pro$6.99/mo · monthly; a 19.99 USD one-time unlock is also offered · $83.88/yr
free tierThe free download includes a handful of cameras; most film stocks, effects, and video modes sit behind Dazz Pro or per-camera purchases.
verified 2026-08-11 · source ↗
Is Dazz Cam free?
The free download includes a handful of cameras; most film stocks, effects, and video modes sit behind Dazz Pro or per-camera purchases. Paid is Dazz Pro at $6.99/mo (checked 2026-08-11).
Vibecode Dazz Cam
Yes. A competent AI coding agent (Claude Code, Codex, Cursor) can build a usable personal Dazz Cam replacement in one session with the prompt on this page. It runs on your own machine or server with no subscription.
How much does Dazz Cam cost?
Dazz Cam costs about $6.99/month (Dazz Pro, checked 2026-08-11), which is $83.88 per year. That's what you save by replacing it with one prompt.
What do I lose by replacing Dazz Cam?
Honestly: dozens of hand-tuned film stocks refined over years of color work; the polished video modes - 8mm, camcorder wobble, stabilization; special-effect lenses like fisheye, prism, and starburst done well; ongoing filter drops that chase whatever look TikTok wants this month; one-tap install for friends who will never sideload anything. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to Dazz Cam?
Yes: GPUImage3 (Metal-based real-time image and video filtering framework for iOS - the plumbing half of this app as a library.). Using prior art is also vibecoding; the prompt is for when you want it exactly your way.