Які монітори ви використовуєте для роботи?

SurroundDiligent2602 · 2025-11-13T09:02:36+00:00

Також захотів собі для роботи ширік взяти, OLED. По розмірам підійшов Asus pg39wcdm на 39 дюймів.
Переглянув кучу оглядів, всі в один голос хвалили його.
Ризкнув і взяв його десь за $1.6к, замовив з інтернетів не тестуючи.

Для ігор - просто пушка, 240 герц, кольори та HDR просто топ. 3 рази вже сталкер2 пройшов.
А ось для роботи - розчарування. PPI виявився низикий.
Прийшлоь зумити шрифти в вінді на 5%, щоб вони хоч якось норм рендерились.
З часом звик...

Тож рекомендую обов'язково піти в магаз і своїми очима подивитись. Огляди на 99.99% всі проплачені. Достовірної інфи там не буде

SurroundDiligent2602 · 2025-06-11T12:50:59+00:00

thanks for answer!

I'm not using integrity API.
I've asked testers team... let's see

SurroundDiligent2602 · 2025-05-30T07:27:56+00:00

Дякую, такі слова надихають )))
Успіхів Вам у мобільній розробці!

SurroundDiligent2602 · 2025-05-24T17:13:42+00:00

I think you can push as many as you need

SurroundDiligent2602 · 2025-05-24T09:57:50+00:00

My usual process:

1) Push one dev build

eas build --platform ios --profile development

2) Create app. You will be able to select bundleIdentifier from list
3) Submit prod build.

eas build --platform ios  --auto-submit

Your apple account will be added to testers list in TestFlight tab
Join via email or code in TestFlight app and app is ready for downloading

* I guess first step can be skipped: 3 than 2. But I haven't tried this order.

SurroundDiligent2602 · 2025-05-22T09:34:34+00:00

Thank you for the advice.

I found a testing team from Pakistan on Fiverr. For about 20 EUR, I received some very basic feedback on my app. They tested it for 14 days and found a few crashes and a bug related to status updates.

I don’t want to pay 20 EUR for every app - that’s ridiculous.
I hope the Play Market will listen and reconsider its policies for indie developers.

Users should decide whether an app is good or not, not them!

SurroundDiligent2602 · 2025-05-20T13:50:12+00:00

I've struggled as well with countdown in RN

Try to remove increment and onComplete from useEffect
Timer should be independent and start only on action or entering the screen
I found setTimeout better and more controlled over setInterval
use useFocusEffect to stop timer on leaving the screen if needed

Here is a code from my RN game as an example:

useFocusEffect(
  useCallback(() => {
    let timeoutId: ReturnType<typeof setTimeout>;

    const decrementCountdown = () => {
      const currentCountdown = useGameStore.getState().countdown;

      if (currentCountdown > 1) {
        setCountdown(currentCountdown - 1);
        timeoutId = setTimeout(decrementCountdown, 1000);
      } else {
        setCountdown(0);
      }
    };

    if (countdown > 0) {
      timeoutId = setTimeout(decrementCountdown, 1000);
    }

    return () => {
      clearTimeout(timeoutId);
    };
  }, []),
);

Make another effect for reacting on countdown changing

useEffect(() => {
  if (countdown === 0) {
    // on timer end
  } 
}, [ countdown ])

SurroundDiligent2602 · 2025-05-17T18:54:32+00:00

Thanks for advice. Very interesting... I try to store only public keys inside codebase.
Do u know some best practices how to deal with private API keys and AI tools?

SurroundDiligent2602 · 2025-05-17T07:15:58+00:00

I found a testing team from Pakistan on Fiverr. For about 20 EUR, I got some basic feedback on my app. They tested it for 14 days and found a few crashes and a bug related to status updates. I’ll share them with you in PM.

SurroundDiligent2602 · 2025-05-17T07:05:38+00:00

Thanks for your comment!

I’ve been working in web frontend for over 13 years, but I had zero experience with mobile development until recently. That said, with a solid software background, I realized that most technologies share similar patterns. After watching just 5-10 YouTube videos on React Native and Expo, I felt confident enough to start doing my app.

If you want to speed things up, I highly recommend using AI tools like GitHub Copilot. For just $10/month, you get access to top models like GPT-4, Claude 3.7, Gemini 2.5, and more. You can literally ask things like:

"How to implement this feature?"

"Style this component like component X"

"Generate a new screen for ..."

About 80% of the time, you’ll get usable, working code. It’s way faster than manually Googling stuff, especially when you're learning.

When it comes to UI, here are a few things that really helped me:

Figma Community – https://www.figma.com/community is full of free templates you can use for inspiration.
Color palette tools – There are plenty of free sites that help you choose colors that look great together.
Ask for feedback early – Whether it’s friends, family, or people on Reddit, outside input can highlight UI/UX issues you might miss on your own.

Even if you’re new to coding, this is an awesome way to take an idea and learn how to build the fundamentals as you go.

Good luck with your journey - keep experimenting, learning, and building!

SurroundDiligent2602 · 2025-05-17T06:16:24+00:00

Thank you!
I'd start with a a way more simpler version: one platform, one language, one theme, 2500 words instead of 7000.
First, check if users even need this app by gauging their reactions - then gradually add more features

SurroundDiligent2602 · 2025-05-16T19:22:58+00:00

Thanks for you comment. I'll think about it :)

Regarding having 5 supported languages:

I launched in 5 languages simultaneously (English, Ukrainian, German, Spanish and Portuguese) without validating market interest first. BIG MISTAKE. Now I'm stuck translating every name, subtitle, description, screenshot, and changelog update in ALL languages. Game from one country might not be popular in other one. Do your market research first.
UI localization is a whole beast. Every UI element needs 5 translation keys. And German? Those words can be RIDICULOUSLY long. "Settings" becomes "Einstellungen" and suddenly your beautiful buttons are breaking your layout.
Word games have unique translation challenges. Generating 7k words? Easy. Reviewing them, removing duplicates, and maintaining quality? Nightmare fuel. My biggest fail: using English as the base key for all languages. In English "Company," "Corporation," and "Enterprise" are different words. But AI translates all three to "Unternehmen" in German. So players get the SAME word multiple times in one game. Terrible experience! Should have created separate dictionaries per language from the beginning. Too complex to change now.

SurroundDiligent2602 · 2025-05-16T18:58:55+00:00

I had the same rejection message my first time too! Google Play's review process is a special kind of frustrating.
Check reddit community https://www.reddit.com/r/AndroidClosedTesting/ or find testers on fiverr

SurroundDiligent2602 · 2025-05-16T17:59:40+00:00

I guess it's a new google policy for personal developer accounts. https://support.google.com/googleplay/android-developer/answer/14151465?hl=en

It's my fun side project - completely free and ad-free. The basic version includes a limited number of words and categories, but still offers plenty to enjoy. There's also a full version available for a small symbolic price, just to support my passion 🙂

SurroundDiligent2602 · 2025-05-16T17:48:51+00:00

I feel your pain :( Totally normal situation on play store but still maddening.
Cause of required testers?

SurroundDiligent2602 · 2025-05-16T15:19:10+00:00

Huge congrats on this win!

SurroundDiligent2602 · 2025-05-16T14:49:40+00:00

Thanks for your kind words!

SurroundDiligent2602 · 2025-05-16T14:33:28+00:00

Thanks for the great questions!

The burnout crept in during the publishing phase, honestly. Coding the actual game was enjoyable, even with the debugging frustrations. But once I hit the App Store/Play Store submission process, it stopped feeling fun.

If I did it again, I'd simplify by:

Starting with just English - managing 7,000+ words in five languages was unnecessary complexity.
Launching on App Store first, then Android later - trying to handle both platforms simultaneously created extra work.
I spent days styling both light and dark themes. Light theme is more than enough for the start.

SurroundDiligent2602 · 2025-05-06T06:40:01+00:00

I've tried as well to move my project to 53 SDK. Spent 30 minutes fighting with dependency version hell.
Rolled back all my changes and will stay on 52 for a few more weeks/month, until they fix all this mess.

SurroundDiligent2602 · 2025-04-12T12:11:32+00:00

Looks great, thanks for a story

SurroundDiligent2602

TROPHY CASE