Haardik Trivedi - iOS Engineer

26/11/2025

🧪 Appium for iOS – Test Like a User, Not Just a Developer

Unit tests are great. XCTest is powerful.
But at some point, you need to know:
👉 “Does my app actually behave the way a real user would expect?”

That’s where Appium for iOS comes in.

Appium lets you:
✅ Automate real user flows – login, purchase, search, navigation
✅ Run the same test logic across iOS & Android (cross-platform tests)
✅ Integrate with CI to catch UI issues before release
✅ Test on real devices & simulators without rewriting all test code

For teams working on multi-platform products, Appium becomes that single test layer which keeps both platforms aligned on behavior, not just implementation.

At the end of the day, tools like Appium remind us:
It’s not enough that the code compiles —
The experience has to pass, too. 💡

Have you used Appium in your iOS projects, or are you still relying only on XCTest/XCUITest?
-

22/11/2025

❤️ Selected for My Dream Job in Bangalore… But I Chose My Family Instead

Life surprised me recently.
I got selected for a dream role in Bangalore — the kind of opportunity I’ve worked years for.
A role that matched my skills, my passion, and my long-term goals.

But sometimes, even when everything looks perfect on paper…
your heart reminds you of your real priorities.

Due to my current family responsibilities, I made the toughest decision of my career —
👉 I said no to the dream job.
👉 I said yes to my family.

And let me be honest —
It hurt…
It was emotional…
But I have no regrets.

Because dreams can be rebuilt.
Careers can restart.
Opportunities can come again.
But family?
Family needs you in the moment, not later.

So here I am — choosing the path that keeps me close to home:
✨ Remote roles (priority)
✨ On-site only in Ahmedabad

With 11+ years of iOS, watchOS & tvOS experience, I’m fully ready to contribute with the same dedication — just from where I’m needed the most.

If you know any opportunity that fits this direction, your support would mean a lot. 🙏

Sometimes the strongest decision isn’t chasing your dream —
it’s protecting the people who helped you build it. ❤️
-

19/11/2025

🤖 Interviewer asked: “Do you use any Copilot or AI tools while coding?”

Yes — and honestly, it has made me a better engineer, not a dependent one.

I shared this in my interview yesterday:
👉 I use AI tools like GitHub Copilot / ChatGPT to speed up boilerplate, explore patterns, generate test cases, and validate ideas…
BUT
👉 I never rely on AI for logic, architecture, or production-critical decisions.

AI accelerates the setup, but the thinking still comes from experience — especially with 11+ years in iOS, tvOS, and watchOS development.

Real developers don’t fear these tools.
We use them smartly — to focus more on architecture, user experience, and solving deeper problems instead of wasting time on repeated code.

AI isn’t replacing engineers.
It’s replacing the time we used to spend on boring parts of engineering. 🚀

Do you use AI or Copilot in your development workflow?
-

19/11/2025

🔁 Retry Logic in iOS APIs – Smart Resilience, Not Blind Repetition

Network calls fail. Not because your code is bad — but because real-world networks are unstable: timeouts, flaky Wi-Fi, server hiccups, DNS issues.

That’s where retry logic makes a huge difference. But it has to be designed, not just “try again 3 times.”

When I think about retries in iOS apps, I focus on:

✅ When to retry
• Temporary issues: timeouts, network lost, 5xx server errors
• Avoid retrying on 4xx (like 400 / 401 / 404) – those are logic/auth issues, not network issues

✅ How to retry
• Use exponential backoff (e.g. 1s → 2s → 4s) instead of hammering the server
• Set a max retry count to protect both user experience and backend
• Combine with cancellation if the user leaves the screen

✅ What to consider
• Idempotency – safe to retry GET, but be careful with POST (payments, orders, etc.)
• Show clear UI feedback – “Reconnecting…”, “Tap to retry”, not silent failures
• Log retry attempts for debugging real production issues

Good retry logic is invisible when it works — users just feel the app is “reliable.”
That’s the real goal.

How do you handle retries in your networking layer?
-

02/11/2025

💔 It Hurts When a Chapter Ends Before It Fully Begins

It’s never easy to write a post like this — especially when you’ve given your best and still have to let go.

Our startup recently ran out of projects and funding, and as a result, our entire team is being released.
My last working day will be in the third week of November.

This one hits harder than expected.
I’ve been the sole earner in my family, raised by a strong single mother who taught me to keep going no matter what — and this situation tests every bit of that strength.

Still, I’m choosing to stay hopeful.
With 11+ years of iOS experience across iOS, watchOS, and tvOS using Swift, SwiftUI, and Objective-C, I’m now looking for a new opportunity — remote or on-site — as a Senior / Lead / Staff iOS Developer.

If you come across any relevant openings, referrals, or leads, I’d deeply appreciate your support.

Sometimes the hardest endings are just disguised beginnings.
-

25/10/2025

💭 Cleared Every Round… But Still No Offer

It’s one of the hardest parts of the job search —
You prepare for days, go through multiple rounds — L1, L2, L3, even client discussions — and still end up with:
📩 “Position on hold.”
📞 No updates from HR.
💬 Ghosted after the final round.

You start to question yourself — Was I not good enough?
But deep down, you know the truth — sometimes it’s not about skill, it’s just timing, budget, or internal changes beyond your control.

The silence hurts. The waiting hurts more.
But giving up isn’t an option — because the right opportunity won’t ghost you, it’ll find value in your consistency.

To everyone still waiting after clearing rounds — you’re not alone. Keep believing, keep showing up. The “yes” is coming — just a bit delayed. 🙏
-

23/10/2025

💭 When Effort Doesn’t Show Immediate Results

Tons of new connection requests sent.
Dozens of personal DMs written with care.
Countless emails, applications, and follow-ups — all sent with hope.

Yet… still waiting.

Sometimes it makes you wonder — is it me, the market, or just timing?

The job market feels quiet right now. Roles open and close fast, and even experienced professionals are waiting longer than expected. But one thing I’ve learned through all this — consistency and patience still matter.

With 11+ years of iOS development experience across iOS, watchOS, and tvOS, I’ve built, delivered, and led projects with pride. I know the right opportunity will come — maybe not fast, but at the right time.

If you’re also searching, don’t lose hope. Keep showing up. Keep applying. Keep believing.
We’re not starting over — we’re just waiting for the right door to open. 🙏
-

20/10/2025

🙏 A Divine Journey Concluded — Shrimad Bhagwat Saptah (2025)

With immense gratitude, I’m sharing that our family successfully hosted the Shrimad Bhagwat Saptah from 15th to 21st September, dedicated to our beloved Pitru (ancestors).

The Saptah was beautifully delivered by
🕉️ Yuva Bhagvatacharya Shree Viralbhai Nakar (Jamnagar, Gujarat) — whose soulful narration touched every heart and filled our home with devotion, peace, and divine energy.

It was a week of reflection, bhakti, and blessings — a reminder that faith and gratitude connect us beyond generations.
For those who couldn’t attend in person, you can watch the full 7-day Saptah here:
🎥 Watch Full Bhagwat Saptah Playlist (It's in Gujarati lanuguag)

https://www.youtube.com/playlist?list=PLjMlP3B-BecxGEoyX7iF5rf7YKyF55vg8

May these divine moments bring light and peace to all.
🪔 Jai Shri Krishna! 🙏
-

The Trivedi family hosts "Shrimad Bhagvat Saptah" in 2025 by Truptiben Ajaybhai Trivedi & Aanal. Kathakar: Shastri Shree Viralbhai Nakar (Yuva Bhagvatachary,...

11/10/2025

🪔 This Diwali Hits Different

While most people are preparing their homes for light and celebration, our startup is facing a difficult reality — with no new projects in the pipeline, our entire team, including myself, is being released.

It’s painful, especially around a festival that stands for hope, light, and new beginnings.
But maybe that’s exactly what this moment is about — endings that make room for something brighter ahead.

With 11+ years of experience in iOS development — working on iOS, watchOS, and tvOS apps built with Swift, SwiftUI, and Objective-C — I’m now open to new opportunities as a Senior / Lead / Staff iOS Developer (Preferably Remote or On-site Ahmedabad, Pune, Bangalore, Noida, Gurgaon, etc.).

If you hear of any openings, I’d be truly grateful for your support, referrals, or even words of encouragement.

This Diwali, I’m not celebrating — I’m restarting.
And maybe that’s a light in itself. ✨
-

10/10/2025

🎯 You Use It Every Day — But Don’t Know the Interview Term For It

One of the toughest parts of interviews isn’t the code…
It’s the terminology.

You’ve probably experienced it too:
💬 Interviewer: “Can you explain back pressure in Combine?”
👨‍💻 You: “I use Combine every day… but what exactly do they mean by back pressure?”

It’s not that you don’t know the concept — you’ve handled async streams, cancellables, and performance issues in real projects.
But the interview language often doesn’t match real-world experience.

Here’s the truth:
✅ You’re already solving these problems daily.
✅ You just need to bridge experience with terminology.
✅ Reading docs or revising core concepts helps turn your work into interview-ready language.

💡 Real engineering is about building.
Interviews are about explaining what you already build.

So don’t doubt your skills — just learn to name what you already know.

Have you faced this gap between daily work and interview vocabulary?
-

10/10/2025

🧠 In the Era of AI & Autocomplete, Whiteboard Coding Feels Outdated

We live in a time where AI assistants, autocomplete, and smart IDEs are part of everyday development — helping us focus on logic, not syntax.

Yet in interviews, many companies still expect developers to write code on a whiteboard or plain notepad — without compiler help, auto-suggestions, or even syntax highlighting.

Let’s be honest — that’s not how real engineering works anymore.

✅ Real-world coding is about problem-solving, design thinking, and debugging
✅ We use tools — not to cheat, but to be more efficient
✅ Great engineers know why code works, not just how to type it out flawlessly

💡 Maybe it’s time interview processes evolve — to reflect how modern developers actually build software.

We don’t debug on a whiteboard. We think, iterate, and improve — just like real projects.

What’s your take — should interviews test problem-solving or manual coding memory?
-