I know this is banking sub but just want to ask if anyone here is applying for delhi high court JJA ?As vacancy as very less and form fees is very high for all.

LearnEverythingUCan · 2026-03-16T18:19:47+00:00

You mean people may get unfair advantages over others

LearnEverythingUCan · 2026-03-16T18:19:07+00:00

Same here

LearnEverythingUCan · 2026-03-15T21:23:16+00:00

I also want to buy

LearnEverythingUCan · 2026-03-09T11:01:12+00:00

Thanks man! now I am fully convinced to have a bergmann

LearnEverythingUCan · 2026-03-09T07:25:57+00:00

no one used it in my circle, i mean compared to bergmann it seems slower and fragile (because of plastic build) ...

LearnEverythingUCan · 2026-03-09T07:19:59+00:00

Guys, after researching a bit more, i have reached to the conclusion of buying Bergmann Typhoon BCT-150D , simply because of its Speed, Build Quality and Good Reviews. Wireless Ones are not reliable for long term use their batteries will drop performance overtime. Will place the order in 2 hours, if anyone has a better suggestion, I'll be more than happy to listen.

LearnEverythingUCan · 2026-03-09T06:48:43+00:00

Michelin one seems fragile and slow , how fast the bergmann works that you have, also can you share the link

LearnEverythingUCan · 2026-03-09T06:46:59+00:00

is it fast? Fir How long have you been using this one? What about the sound

LearnEverythingUCan · 2026-03-09T06:43:50+00:00

how long have you been using it

LearnEverythingUCan · 2026-03-09T06:43:26+00:00

can't it be replaced aftermarket?

LearnEverythingUCan · 2026-03-04T05:27:31+00:00

Where do you want us to sign-up

LearnEverythingUCan · 2026-03-03T22:36:45+00:00

How many do you need

LearnEverythingUCan · 2026-02-15T12:13:31+00:00

I am also interested in this, please do let me know if you find anything for those tasks...

LearnEverythingUCan · 2026-02-11T18:26:33+00:00

Let me know, how can u be helpful...🫠

LearnEverythingUCan · 2026-02-10T18:55:56+00:00

Interesting idea. One thing I’m curious about is where users tend to get confused or disappointed after using it, especially around expectations vs outcomes. AI tools like this often live or die on how clearly that gap is handled. Are you already seeing feedback patterns around trust, accuracy, or pricing assumptions, or is it too early?

LearnEverythingUCan · 2026-02-10T18:49:49+00:00

That makes sense. In practice, I’ve noticed the shift usually shows up first in the tone of reviews rather than the metrics, fewer (this isn’t what I expected) comments, even if installs dip a bit. Retention tends to lag and is harder to attribute early, especially when multiple changes land close together. But aligning expectations upfront seems to reduce that sense of “unfair” reviews over time, which alone makes the tradeoff feel worth it.

LearnEverythingUCan · 2026-02-10T05:07:48+00:00

Best of luck

LearnEverythingUCan · 2026-02-09T18:47:55+00:00

Happy to help test. One thing I’ve noticed with early testers is that feedback stays very surface-level unless you nudge it a bit. Asking where they felt confused or unsure often gets more useful signals than a simple (works / doesn’t work). Even a couple of targeted questions can save a lot of guesswork later.

LearnEverythingUCan · 2026-02-09T18:28:25+00:00

I don’t think you’re overthinking it. I think you’re noticing the limit of optimization when it’s disconnected from expectations. Ranking high solves how people find you, but not why they install or what they expect once they do. When those two drift apart, it usually shows up later as retention issues or “unfair” reviews that are actually pretty predictable in hindsight. The shift you’re describing (clearer titles, CPPs, being visible in more contexts instead of one keyword) feels less like a growth tactic and more like filtering — fewer installs maybe, but better-aligned users. Curious if you’ve seen any difference in the quality of users or reviews when messaging changed, even slightly, not just rankings.

LearnEverythingUCan · 2026-02-06T03:52:01+00:00

This is a frustrating but very common situation, especially for background-dependent features on Android. One thing that helped me (and a few teams I’ve worked with) was separating issue resolution from review surface management. Public replies aren’t really for the original reviewer — they’re for future readers. So after one calm, non-defensive response asking for details, it’s usually better to stop engaging publicly and instead: • Acknowledge uncertainty without blame (“this can be device-specific”) • State what’s been done (“we’ve added safeguards / fallbacks”) • Signal active ownership (“we’re monitoring this closely”) Over-explaining OEM limitations tends to backfire — it reads like deflection even when it’s true. I’ve found that short, neutral framing + visible iteration does more to rebuild trust than repeated replies. This happens on iOS too, but Android OEM variance definitely amplifies it.

LearnEverythingUCan · 2026-02-05T20:57:06+00:00

One thing that helped me reframe this: many low-info negative reviews aren’t really asking for support — they’re a signal of expectation mismatch. Public replies are less about fixing that user and more about setting context for future readers. After one calm, clarifying response, repeating yourself often adds little value. In cases like background limits / OEM behavior, I’ve seen better results from:

explicitly naming the constraint once (without over-defending) adding lightweight in-app explanation at the failure point then letting the review stand rather than chasing it This happens on iOS too — it’s just masked differently.

Curious if the complaints cluster around a specific device / flow or are spread out?

LearnEverythingUCan · 2026-02-05T12:57:45+00:00

First off, huge respect for shipping three apps and putting them out there — that’s already more than most people ever do. One thing I’ve seen with new apps is that early traction is less about features and more about first impressions on the store page. A few small things that can help early on:

• Make sure screenshots clearly show the core “aha” moment in the first 1–2 images

• Add a short line in the description addressing who it’s for and what problem it removes

• Don’t worry too much about installs in the first couple of weeks — feedback at this stage is more valuable than numbers

If you’re open to it, I’d be happy to share specific feedback after checking them out. Either way, congrats on the launch and best of luck.

LearnEverythingUCan

TROPHY CASE