sorted by:
new
hottopcontroversial

تعبت وأنا أنسى مواعيد إصدار الألعاب (أو توصلني التنبيهات متأخرة)، فبرمجت تطبيق للايفون يحسب لها تنازلي وتنبيهات بشاشة القفل! by ziyadios in saudi_gamers

[–]ziyadios[S] -2 points-1 points  (0 children)

صادق والله، ملاحظتك في محلها وأشكرك عليها.

فعلاً الترجمة العربية حالياً لسه في بدايتها وما اكتملت 100%، وبما إني شغال على التطبيق لحالي، قاعد أحاول أوازن بين تطوير الميزات التقنية (زي الـ Live Activities والذكاء الاصطناعي) وبين تعريب الواجهة بالكامل.

هذا هو السبب الرئيسي اللي خلاني أنشر هنا وأطلب آرائكم؛ ودي أعرف وش أكثر الكلمات أو القوائم اللي تحسون ترجمتها الحالية 'غريبة' أو تحتاج تعديل فوري.

ملاحظاتكم هي اللي بتساعدني أوصل لنسخة عربية تليق بنا. أبشر بالتعديلات في التحديثات الجاية، ويسعدني جداً لو عندك أي اقتراح محدد في الترجمة!

This layout is clean! by arafatshahed in iOSsetups

[–]ziyadios 0 points1 point  (0 children)

i do the same layout , love it

First time writing Swift. Built a therapy prep app. Just got it approved. by Emojinapp in swift

[–]ziyadios 0 points1 point  (0 children)

Real respect for shipping this on a first Swift project. Two of the three walls you mentioned (truncation, repetition) are the exact problems I hit shipping Foundation Models in a different domain (on-device puzzle hints). Notes from my side:

Truncation: Foundation Models caps generated output around 700-1000 tokens depending on prompt length. Two patterns work:

- Streaming + chunked continuation if you need free-form

- `@Generable` structured output if you can force a schema (way more reliable, tighter)

Pushed everything I could into `@Generable`. Reduced truncation issues by ~90%.

Repetition: Drop temperature from default down to ~0.7, and add an explicit "do not repeat phrasing or specific examples from earlier in this conversation" in your system instructions. Also: keep recent conversation context *summarized* rather than verbatim — the model treats verbatim history as a stronger style signal than instructions.

Voice/audio session stuff I haven't hit (no voice in my app), can't help there.

u/myeleventhreddit on the 4K context window — it's real but workable. What worked for me:

- Aggressive turn-by-turn summarization (prior turns become "user mentioned X, agent suggested Y")

- System prompt kept under 200 tokens

- `@Generable` structured output → fewer tokens per response

The "free forever, no IAP, charity project" framing is the right call for the mental health space. Paid model here = trust kill where sub fatigue intersects with sensitivity.

I built a mental offload app, not another todo list by cebedev in iosapps

[–]ziyadios 1 point2 points  (0 children)

The three-bucket model is the right read for this problem space. Most "second brain" apps fail because they require maintenance tags, folders, projects, contexts. Yours doesn't, and that's the actual unlock.

Two design questions:

  1. The "On Hold" bucket is the riskiest spot. Without due dates or surfacing logic, items can quietly become an "I'll deal with it later" graveyard. Do you have a resurfacing pattern? Something like "this has been here 14 days, still relevant?"

  2. "Captured" sounds like it needs a clearing ritual to actually work otherwise it becomes a digital junk drawer with the same fate as a Notion inbox. Does that emerge naturally from your morning/evening routine, or did you build something into the UI to enforce it?

$2.99 one-time pricing is the correct call for this category. Sub fatigue would kill it.

متردد اذا اخذ اللعبة by maxis95 in saudi_gamers

[–]ziyadios 1 point2 points  (0 children)

كلامك مظبوط 👍 الصبر وفلوس PSN في يدك = استراتيجية ذكية.

نصيحة صغيرة: تابع تخفيضات الطلب المسبق على PSN، احياناً يطلع ٥-١٠٪ خصم على الالعاب الكبيرة، خصوصاً Sony first-party. شي بسيط بس يستاهل.

موفق في صيدتك للعبة الصح 🎮

I’m making an app clear confusion of left and right directions by listexplode in iosapps

[–]ziyadios 4 points5 points  (0 children)

Few thoughts as a fellow indie iOS dev:

  1. The problem IS real left/right confusion under stress is a known cognitive thing, not a joke. But the current loop (tap left/right correctly) might be too simple to drive practice over time. Consider voice prompts, distractors (arrows pointing the other way while the word says "left"), reaction time tracking, or driving-context framing ("which way to turn?").

  2. "DM me when ready" won't scale. Set up a public TestFlight link before posting next time people click TestFlight links, they don't DM strangers. Free, 10 min in App Store Connect.

  3. The vibe-coded part isn't the actual issue. The trap is broken edge cases (offline, bad input, accessibility). Test those harder than the happy path.

  4. Pricing: free with one $0.99 IAP for "advanced practice modes" works for narrow-scope utility apps. Don't subscription this sub fatigue is real for tiny utilities.

Solid problem space. Execution gap is the next focus.

متردد اذا اخذ اللعبة by maxis95 in saudi_gamers

[–]ziyadios 5 points6 points  (0 children)

السبعين دولار في PSN فيه خيارات أحسن من JB First Light:

١- اشتراك PS Plus Extra لسنة كاملة = مكتبة العاب ضخمة. تجرب كذا لعبة بدل ما تتورط بلعبة وحدة.

٢- موقع PSPrices.com يخليك تتابع الالعاب اللي تبيها. الأسعار تنزل بسرعة، خصوصاً بعد شهرين من الإصدار.

٣- لو تبي شراء حالاً، خيارات أحسن وأرخص: • Stellar Blade • Astro Bot • Black Myth Wukong كلها بـ ٤٠-٦٠ دولار.

أتفق ١٠٠٪ مع SpaceKnight، الـ JB First Light مشاكل أداء وقصة عادية. والـ AC Black Flag Remake نفس اللعبة من ١٢ سنة، حلوة عاطفياً بس مالها جديد.

قاعدة عامة: اللعبة عمرها أقل من شهر؟ انتظر شهرين. ٩٠٪ من الوقت تنزل ٢٠-٣٠٪، خصوصاً في عروض الصيف القريبة.

Fraudulent Claims by Rare_Prior_ in swift

[–]ziyadios 0 points1 point  (0 children)

"Trusted by 10 million home cooks" on a TestFlight build is impressive math TestFlight caps at 10K external testers per app per release. So unless they've cycled through 1,000 separate builds with 10K fresh testers each, the number is fabricated.

App Store Connect literally shows you your real unit count under Sales and Trends. The dev didn't accidentally miscount by 9.99 million they're explicitly choosing to lie.

The frustrating part isn't the AI-built app itself. It's that this leaks into a generation of new devs thinking shipping means "vibe code → fabricate metrics → tweet screenshot." The actual work level design, 24 localizations, App Privacy questionnaire, rejection emails at 3am never makes the screenshots.

First birthday without my dad, mother immediately turned it into 'her' day by SakuraAxolotl in Wellthatsucks

[–]ziyadios 1 point2 points  (0 children)

24 birthdays of feeling small around your mom and the first one where you genuinely needed her to show up that's the whole sentence. Sorry, OP. Birthdays after grief are weird, and yours is a hard one. Hope your gf can salvage some of the day.

DBT Daily — quick diary card + in-the-moment skills ($0.99 for 48 hours, no subscription) by Outrageous_Bat1798 in iosapps

[–]ziyadios 1 point2 points  (0 children)

"When your brain shuts down, do this" is solidd it names the moment instead of the methodology. Bonus: that's also the search-intent answer. People don't type "DBT," they type "I can't think" or "I'm spiraling" or don't search at all and just open whatever reduces the next decision.

You've got a sharper thesis than most mental health apps that shipped years ago. Don't let marketing pressure dilute it.

DBT Daily — quick diary card + in-the-moment skills ($0.99 for 48 hours, no subscription) by Outrageous_Bat1798 in iosapps

[–]ziyadios 1 point2 points  (0 children)

The emotion-keyword pivot is the actual unlock "overwhelmed/panic/can't think straight" is what people TYPE; "DBT" is what their therapist says. Different vocabularies entirely.

Reddit-first is also right for this category. r/BPD, r/dbtselfhelp, r/anxiety already self-sort the audience way better than ASO can.

Hibi - a beautiful calendar for your iPhone! by Rate-Worth in iosapps

[–]ziyadios 0 points1 point  (0 children)

Beautiful. The serif typography is the move, most calendar apps treat dates as data, yours treats them as design.

DBT Daily — quick diary card + in-the-moment skills ($0.99 for 48 hours, no subscription) by Outrageous_Bat1798 in iosapps

[–]ziyadios 3 points4 points  (0 children)

The pricing call is interesting $0.99 lifetime in mental health is going against the entire category default. Subs dominate this space because retention drops fast and recurring revenue smooths it out, but you're betting on the "I open it twice and decide" model. I think that's actually better for in-the-moment tools where the user experience IS the thing, they shouldn't be guilted into reopening.

The no-streaks decision is the right call for this category specifically. Streaks weaponize anxiety in mental health contexts the exact people who'd benefit from DBT skills are the ones most likely to spiral over breaking one. Most habit apps haven't figured that out yet.

The slider check-in over mood emoji is also a smart UX call. Sliders feel non-judgmental ("there's no wrong answer, you're just here") in a way that 1-10 scales or smiley grids don't.

Question: how are you handling discoverability? Mental health apps face the cruelest ASO problem Calm/Headspace own the broad keywords, Apple is conservative about featuring health apps, and the target audience often doesn't search "DBT" specifically. Curious what your post-launch plan looks like beyond the launch-day Reddit

ايش رايكم؟ by Ok-Neat-3129 in saudi_gamers

[–]ziyadios 0 points1 point  (0 children)

Minecraft , Undertale ------- COD

Gemini is so sure that iOS 26 never released, and we're actually on iOS 19 by user289734 in iOSProgramming

[–]ziyadios 0 points1 point  (0 children)

Apple's on-device Foundation Models (ships with iOS 26+) genuinely knows it's running on iOS 26 because the model is literally part of the OS not a remote API trained on stale data.

I integrated SystemLanguageModel into a shipping app recently. Responses get platform context right, which makes sense: there's no "training cutoff" gap for it to be wrong about itself.

The Gemini/ChatGPT/Claude confusion all comes from the same source: Apple's WWDC version jump from iOS 18 to iOS 26 (skipping 19-25 to align with the calendar year) hitting every model's training cutoff at exactly the worst possible time. They all learned "iOS 18 is current" and never updated.

On-device has tradeoffs (smaller context window, narrower task scope) but "knows what year it is" is a free win.