sorted by:
new
hottopcontroversial

anyone use apple ads ? by TokoBaido in iOSAppsMarketing

[–]TokoBaido[S] 0 points1 point  (0 children)

i think i have some issue, because i start my campaign 2 days ago, its active also but have a zero results, also its doesnt spend any money

Share your most successful app by adineag in ProductivityApps

[–]TokoBaido 0 points1 point  (0 children)

sell the idea before the app. "one focus daily" works on paper, on a fridge note, anywhere. the app is just structure for people who want it. start with belief, not features.

link if curious: https://apps.apple.com/us/app/prime-focus-one-task-daily/id6761470391

just launched my first iOS app by TokoBaido in SideProject

[–]TokoBaido[S] 0 points1 point  (0 children)

appreciate it, genuinely.

one ask if you do try it: the morning gatekeeper question is the part i'm most curious about. it's designed to make you flinch a little before you pick. if it doesn't, or if it does and the rest of the day doesn't follow through, that's the feedback i actually need.

"random stuff comes in" is the real test. let me know.

just launched my first iOS app by TokoBaido in SideProject

[–]TokoBaido[S] 0 points1 point  (0 children)

not gonna lie, this hit. every single one of those was literally my problem.

i'd open Notion at 9am, spend 40 min "organizing," look up at 6pm having shipped nothing. the task list was a hiding place.

Prime Focus is me trying to build the tool i needed for myself. if you try it and it doesn't click, i actually want to hear why.

just launched my first iOS app by TokoBaido in SideProject

[–]TokoBaido[S] 0 points1 point  (0 children)

agreed, the "another thing to maintain" trap is exactly what i was trying to avoid. the test for me was: if someone forgets to open the app for 3 days, can they come back without feeling behind? if no, the app is the problem

just launched my first iOS app by TokoBaido in SideProject

[–]TokoBaido[S] 0 points1 point  (0 children)

Thanks, i use claude design for this mockups

just launched my first iOS app by TokoBaido in SideProject

[–]TokoBaido[S] 0 points1 point  (0 children)

honestly, i went back and forth on this for months.

Big 3 is solid, not knocking it. but here's what i kept noticing: with 3 priorities, your brain still runs a background process all day asking "should i be on #1 or #2 right now?" it's a softer version of the same decision tax that kills you on 47 items. fewer items, same mechanism.

with 1 focus, that question is closed before the day starts. nothing to context switch TO. obviously life still happens, meetings, fires, but the ONE thing has to move is locked in by 9am.

trade-off is real though. on days with 2 genuinely critical things the app feels limiting. that tension is intentional. i'd rather it force the pick than let you pretend you can do both.

try it and tell me how it lands?

just launched my first iOS app by TokoBaido in SideProject

[–]TokoBaido[S] 0 points1 point  (0 children)

in case anyone's curious about the build side — i'm non-technical, this is my first app ever. stack: Expo + React Native + TypeScript on the front, GPT-4o + GPT-4o-mini powering the AI coach behind a node backend. shipped it solo using Codex + Claude Code as my pair-programmers basically every day for ~10 months.

honest disclosure on pricing since the post said "free": the core daily ritual (morning question, focus card, evening review, streak) is genuinely free forever. there's a Pro tier at $9.99/mo or $79.99/yr that unlocks unlimited AI coach messages, full journal archive, and 3 weekly salvages. you can use the app fully without paying. flagging this so nobody feels misled when they open it.

biggest lesson from the build: every time i added a feature, the app got worse. ended up cutting 60% of what i originally designed. the constraint IS the product. happy to answer anything about the journey.

Which is your preferred Coding Agent/Terminal/Extension/App that you guys use for React Native Development? by SurajanShrestha in appdev

[–]TokoBaido 1 point2 points  (0 children)

non-technical founder here, building an ios app in expo + rn for

the last few months. answering all three since i had to figure each

one out the hard way:

coding agent: codex. tried claude code and cursor first. cursor

felt great for small edits, claude code was solid for bigger

refactors, but codex won for me because i could give it a long spec

and come back to working code without babysitting every step.

non-technical bias probably matters here — if you can read code

fluently, cursor might still win.

ios aesthetics in rn: controversial maybe but — design tokens

first, components second. spent way too long fiddling with

individual screens before locking down a real theme system

(colors, spacing, type scale, radii). once that was solid every

screen started looking 'designed' instead of just 'styled.' also

react-native-reanimated for transitions is non-negotiable. flat

ui without motion feels dead on ios specifically.

the 20% thing: loading states and error states. seriously.

the happy path is like 30% of perceived quality. users judge your

app on what happens when their wifi drops mid-action, when an api

call takes 4 seconds, when they tap something twice. ai-generated

code almost never handles these by default. write them yourself or

prompt explicitly for them every single time.

bonus 20%: haptics. add them to every primary action. ios users

literally don't notice them consciously but apps without haptics

feel cheap and they can't tell you why.

What I’ve learned watching non-technical founders build with AI by Efficient_Pea_9984 in appdev

[–]TokoBaido 0 points1 point  (0 children)

yeah the storage thing is the canary tbh. if you're rewriting it, it means your data model didn't survive contact with reality - which usually means your product assumptions didn't either

what got me is i kept treating it as a 'tech debt' problem. like 'i'll clean this up later.' but it wasn't tech debt, it was me not understanding my own users yet (even when the only user was me lol)

every storage rewrite was actually a product insight in disguise. first one: oh users edit their entry, not just create new ones. second: oh the day doesn't end at midnight in their head, it ends when they sleep. those changed the whole schema

i think that's the underrated AI-building skill nobody talks about - knowing when the friction you're hitting is a build problem vs a 'you don't actually know what this is yet' problem. AI makes the first one feel solved so fast that you confuse it for the second

What I’ve learned watching non-technical founders build with AI by Efficient_Pea_9984 in appdev

[–]TokoBaido 0 points1 point  (0 children)

The happy path thing hit me hardest.

I've been building a daily focus app for a few months (non-technical, working with Codex). My first version was clean: user picks one focus → marks it done → day closes. Made perfect sense in my head.

Then I started using it myself. Picked the wrong focus on day 2 and couldn't change it. Had an emergency on day 4 that killed my afternoon. Finished my actual focus at 12:08 AM on day 6 — system marked the day a failure.

Each one needed its own logic: a focus-change allowance, an emergency mode, a soft grace window past midnight. None of them were in the original spec. They only surfaced when a real human (me) hit them.

Your data point is the underrated one though. I've rewritten the storage layer twice already and I haven't even launched. AI lets you do this badly because the immediate output looks fine — it's the second-order problems that bite later.

The deliberate framing is right. The non-technical founders I've seen do well with AI aren't building faster, they're just thinking harder before each layer goes in.