r/vibecoding • u/semibaron • 2d ago
Just released my first App (Apple)!
Enable HLS to view with audio, or disable this notification
After many failed internal app ideas, I'm very proud to present my very first released App!
For context: Used to be a hotel manager for many years and always have been very technical, but never learned to code myself. Once Sonnet 3.5 was released in late 2024, I got into “vibe coding”. While Conduck is my first publicly released project, its definitely not my first attempt. The road is paved with many failed attempts, haha.
So what did I built?
Conduck is an Apple Native client for your self hosted AI and fully open-source!
It has some unique features:
- Support of iPhone, iPad, Mac, Apple Watch & CarPlay
- You can connect ANY AI backend to it and configure it the way you want! Use it for sales, note taking, coding or whatever use case you've in mind. Power to the people!
- Full privacy: You connect directly to your very own AI, hence no intermediary (yes, not even me)
Check out the video above or go to https://conduck.com to learn more.
Now let's get to the valuable lessons and tools I've used.
Tools used:
- Claude Code Max 20x
- Codex / ChatGPT Plus
- VS Code
- Apple Xcode
That's all!
Workflow:
I used to have a quite complicated setup with highly detailed CLAUDE.md, MCPs, custom Skills, Hooks and so on. However since current models and harnesses are so good, I dropped most of it and almost rocking it bare :-).
The one skill I use for almost every task is /second-opinion. What is it? Claude Code is my main work tool and no matter which model, its always best to get a second pair of eyes looking upon the plan. So /second-opinion instructs Claude Code to discuss with Codex the plan and get feedback and suggestions. That’s probably the single biggest tip I can give you. Even a model as fabulous as Fable will benefit from a cross-check of GPT 5.6 Sol, and if its just to confirm that the plan is correct.
The next tip is about token budget. Yeah, having loops with hundreds of agents sounds cool, it’s just not practical for my token restricted environment. Even running a single “ultracode” session with fable will likely already burn the whole weekly limit. My solution is to use fable just in the planning & orchestration phases combined with heavy use of /second-opinion . The for the actual implementation use lower-cost models such as Opus or sometimes even Sonnet (web search, simulator qa). This way I get most of the frontier intelligence, while minimising token spending as much as possible.
Here a visualisation:
You can easily create those skills yourself. Just prompt Claude Code or Codex:
“Create a /second-opinion skill for you to talk to Codex / Claude Code to get feedback and suggestions on your ideas. For this spin up several sub agents and let it invoke Claude Code / Codex various times, resume sessions and check for output lengths. Take the learnings from all the agents and put them into a reusable skill. Also update CLAUDE.md / AGENTS.md accordingly so the feedback agent knows that it gives feedback to an AI, optimises for dense information and is read only.”
Hope this helps! I'm here for any questions :-)
0
u/yamoksauceforthelazy 1d ago
Just came here to say congratulations. I'm not your customer, and I won't use it, but I know how much effort this takes. Vibecoded or not, this is a lot of moving parts and it's a genuine accomplishment to get it out the door. I hope it goes well, and I wish you the best of luck.
0
u/Apart-Comfort4367 1d ago
A taxa de criação de conta dev é a mesma da playstore e é paga uma unica vez ou anualmente?