Plaid AI

Plaid AI AI

Plaid AI AI

Plaid AI AI

Plaid AI AI

Plaid AI AI

Plaid AI AI

Plaid AI AI

Plaid AI AI

Plaid AI AI

Plaid AI AI

Shipped a production iOS app with Claude as a non-technical PM in 2.5 months. What I learned, what worked, what broke, and the moment Claude said "trust me bro, it's fixed"

I'm a product manager with 10+ years of experience and zero coding background. I just shipped my first iOS app in 2.5 months (20-25 hours a week) using Claude as my coding partner. Posting here to share my learnings, my workflow (would love feedback!) and a hilarious hallucination. Would love to hear your funny hallucinations. When I asked Claude to estimate the total build time at the start, it quoted 8 months. I had the first complete local build running in 2 weeks and felt invincible. Then I spent the next 2 months doing the other 80% of the work, which was honestly a slog. What I learned about working with Claude on a real production codebase: Spec before you vibe I used the plaid.build skill (no affiliation, just a fan) to put together a product vision doc, roadmap, and requirements doc before I wrote a line of code. It forced me to make architecture decisions upfront, sparring with Claude, instead of discovering halfway through that my data model was wrong. This is probably the highest-leverage thing you can do. Non-technical folks, it will help you make architecture choices and write out tech specs. Technical folks, it will help you define your go to market plan and tightly scope your MVP. Two days spent with this skill including reading the docs and providing feedback saved me probably two weeks of "Claude why is this broken" debugging on the wrong foundation. I also tried asking Claudes built in skills like /architecture and /design-system but the feedback they gave me, while good, blew up my requirements and was way more than what I needed for an MVP. If I'd listened to their advice it would have taken me probably 4-5 months to launch on the app store. Do spikes Claude recommends any unfamiliar provider? Do a 1-2 hour spike to make sure AI isn't hallucinating and the provider actually meets your needs. Doing this would have saved me a very painful week. Once I gave up on the first provider Claude recommended and did spikes, I was able to choose and implement a working solution in less time that I spent arguing with the original provider. Where Claude carried me Anything well-documented and pattern-heavy: Clerk auth setup, basic CRUD, scaffolding screens, file structure conventions, copy generation. Ask Claude for it's experience and confidence level with each piece. I set up Clerk in 3 hours feeling like a genius. I got a usable settings page in 15 minutes. This is the part of the workflow that genuinely feels like magic, and it's also the part you should expect to work. Where Claude broke down Front-end fiddling. I spent 3 hours debugging a single X close button before giving up with "good enough." My designer friends will cry when they see it it's honestly bad. Claude can scaffold a UI but precision pixel-level interaction work is where it ran out of road for me. Front end development is generally painful and AI still hasn't cracked it. Anything involving a third-party provider where you have to do a lot of configuration in their portal. I spent a full week getting RevenueCat integrated correctly, and apparently RevenueCat is one of the simpler payment integrations. I now understand every developer who has ever complained about Stripe. Maybe an AI browser where it can see your browser and do things for you would have helped, but I don't trust any AI enough yet for this. Real-time video with Picture in Picture support. Claude's first-pick video provider couldn't actually do PiP properly, despite Claude being highly confident it could. I spent several days trying to make it work before reverting to traditional dev practice: 1-2 hour spikes on the next 3 contenders, picked a winner based on actual results, implemented working PiP faster than my original failed attempt. Lesson learned: when Claude is stuck in a loop trying to make X work, swap X out and try alternatives rather than pushing through. Or better yet, do spikes first before locking in your architecture choices. The "trust me bro, it's fixed" moment After multiple failed attempts on a single stubborn bug - HOURS - I was frustrated, Claude was frustrated. After 2 hours Claude basically started saying "no need to test this again, trust me bro its fixed" lol!. For my next app, I'm spending time early on to set up some automated visual regression testing so Claude can't hallucinate as much. Code review process After code was ready, I would do manual testing and ask Claude to fix bugs. Then I would: Run ALL THREE of these built-in skills sequentially against the uncommitted changes. Do not skip any — each one catches different issues: 1. \/security-review\ — Identify security vulnerabilities in the new code. Fix any issues found.`` 2. \/simplify\ — Check for unnecessary complexity, duplication, or over-engineering. Fix any issues found.`` 3. \/review\ — General code review for quality, correctness, and best practices. Fix any issues found.`` Then commit push pr When I was planning out my PR review process, Claude told

Chatgpt now has ads, openai killed Sora,the IPO narrative is writing itself

Openai launched a personal finance feature for pro users two weeks ago so you link your accounts via plaid and gpt can see your balances, transactions, subscriptions, investments and upcoming payments. So you can ask it where am I leaking money and it answers from your actual data. I have been using it for about a week and honestly its more useful than I expected,the subscription audit alone was worth it and i found three things i had forgotten i was paying for . The thing that impressed me most was that the reasoning actually applies to your situation,i mean generic financial advice from ai has always been the weakest use case because its all averages but when the model knows your actual cash flow it stops sounding like a personal finance blog. For context on the scale of what this could become plaid says over 200 mil people already ask gpt personal finance questions every month without any account access and thats a lot of people who would immediately benefit from the upgrade. Curious who else has tried it and specifically does anyone know how it handles edge cases like irregular income or multiple income streams? submitted by /u/NewspaperEqual9619 [link] [comments]

Is Personal Finance "preview" a "dark practice"?

The preview is worthless. Plaid can't connect to many major financial institutions. This is well known: https://help.aura.com/s/article/plaid-bank-connectivity-issues OpenAI could have addressed the problem by working out arrangements with multiple aggregators, as Monarch does: https://www.monarch.com/connection-status So why didn't it? Is the dysfunctional "preview" a dark practice, intended to trick users into revealing whether they're interested in a product that OpenAI knows it can't yet offer? If users aren't interested, OpenAI can skip negotiations and contracts with other aggregators. Some companies deserve the benefit of the doubt. Not OpenAI. Many recent posts/comments in r/ChatGPTPro have documented its dark practices—involving $100/mo Pro, the web UI, memory claims, and other matters. If such practices were benchmarked, OpenAI would top the charts. submitted by /u/Oldschool728603 [link] [comments]

Does switching between AI tools feel fragmented to you?

I use a handful of AI tools every day and it’s getting kind of annoying. Tell something to GPT and Claude acts like you never said a word - like, what? Feels like each agent lives in its own little bubble and I’m the one copying context around. That means lots of repeated context, broken workflows, and redoing integrations, which slows me down. Been thinking: shouldn’t there be a Plaid-ish layer for AI memory and tools? connect once, share memory. Imagine a single MCP server that handles shared memory and permissions, so all agents know the same stuff. Could remove a ton of friction, right? not sure if that exists already or I’m just missing something. How are you folks handling this now? any hacks, tools, or setups that actually work for you? submitted by /u/mpetryshyn1 [link] [comments]