Had a thread rejected recently, still not fully sure why. Got me wondering about a few things and figured i'd just ask directly instead of guessing.
Does getting a thread rejected affect your account in any way, algorithm, visibility, standing, anything like that? or is it just a one-off, no consequence, try again kind of thing?
Also curious how the approval process actually works. is it a human reviewing each thread, some automated filter, a mix of both? trying to understand what actually triggers a rejection so i'm not accidentally repeating the same mistake without knowing what it was.
If anyone from the team or anyone who's been rejected before can share how this actually works, would genuinely appreciate it.
Trust is especially important when an app can access location, motion sensors or emergency contacts.
However, transparency is not always as simple as publishing everything. Sharing source code and data flows can help independent review, while exposing detailed detection logic or security controls could also make a safety system easier to bypass.
Which information would actually help you decide whether to trust a personal safety app?
Would you look for a clear privacy model, permission explanations, selected public source code, independent security reviews, data-retention controls, or something else?
Everyone warns you about the time, the money, and the stress. Nobody warns you about the specific moment you realize you cannot hold all of it in your head anymore, and that moment tends to arrive quietly instead of announcing itself. Mine came the day I found out a repeat client had not booked in six weeks and I had no idea until she mentioned she found someone else. Curious what your version of that moment was, and whether it changed how you run things afterward, or just made you more anxious about missing the next one.
I noticed the pattern only after it had already cost me a client. If a number lives only in your head, or only gets updated when you happen to remember, that is memory, not tracking, even if you would call it tracking if someone asked. It looks fine right up until the moment it does not. Curious what tipped you off that you had crossed that line somewhere in your business, was it a specific mistake, or something you only noticed looking back.
Twenty-two years is a long time to run a business in Japan, and I've got some name recognition to show for it. Switch to English, though, and nobody knows me at all.
Right now I've got around 10 finished products, which means marketing is eating up most of my time. My approach in Japan has always been search-first, and I'm staying with that. After that comes AppSumo, then Product Hunt. I joined PH back in September, mostly because I wanted somewhere English speakers could actually find my work.
Search, though, is going to take a while. So I went ahead and created an X account. On top of that, I keep hearing that posting on LinkedIn pays off.
Linkedin's been full of "ai is coming for your job" posts since astra dropped. Genuinely not feeling that. Feels more like it'll make my actual work easier, more productive, not obsolete.
Might be naive, might be right, not sure yet. But curious what the actual builders here think, not the linkedin doom posters, people who use ai tools daily to ship things.
Does something like this genuinely worry you, or does it just feel like another leverage tool making the work faster.
It s easy to let client commitments swallow your calendar whole. Because client work brings immediate revenue internal products usually take a backseat whenever a deadline gets tight.
I've tested setting aside specific days or taking on fewer clients but unexpected client requests usually ruin the system within a few weeks. Balancing direct service income with long-term software development needs a far more realistic routine.
Have you successfully managed to split your week between client tasks and your own app or did you eventually have to drop client work altogether?
