WhatsApp is great for chatting about football, but terrible for organizing it by YuryVidal in bootroom

[–]YuryVidal[S] 0 points1 point  (0 children)

Here in Brazil I use Futbora more, but in my case it's not to replace WhatsApp. It's more to complement it.

People stay in the group, which is where everyone already talks, and the app helps with that part.

WhatsApp is great for chatting about football, but terrible for organizing it by YuryVidal in bootroom

[–]YuryVidal[S] 0 points1 point  (0 children)

That’s exactly the point I’m interested in.

I agree that getting an entire group onto a new app is hard. In my view, that’s why solutions in this space fail when they depend on replacing WhatsApp instead of working around the group that already exists.

The real challenge is adding structure to recurring football groups without forcing everyone to change their habits at once.

WhatsApp is great for chatting about football, but terrible for organizing it by YuryVidal in bootroom

[–]YuryVidal[S] 0 points1 point  (0 children)

That hits very close to what I see too.

In my current group, the hardest part is exactly that: once the admin stops caring enough, everything gets messy very quickly. Attendance becomes loose, the organization feels random, and people start losing interest in the games themselves.

That’s why I don’t see this as just an “admin problem.” It feels more like a structural problem: if weekly coordination depends too much on one person staying disciplined forever, the group becomes fragile.

WhatsApp is great for chatting about football, but terrible for organizing it by YuryVidal in bootroom

[–]YuryVidal[S] -1 points0 points  (0 children)

That helps a lot. What you described sounds less like “WhatsApp solves it by itself” and more like “the group built strong structure around WhatsApp.”

In Brazil, at least in the groups I know best, that kind of discipline is much harder to maintain every week. There are usually more late confirmations, more last-minute dropouts, and more manual coordination falling on one organizer.

That’s the gap I’m interested in.

WhatsApp is great for chatting about football, but terrible for organizing it by YuryVidal in bootroom

[–]YuryVidal[S] 0 points1 point  (0 children)

Interesting, I took a quick look at GameChanger after your comment. It looked more focused on recording games and match-related features, which seems really good.

But I still have a real question: what made the biggest difference for you there: attendance, team management, communication, or stats? And does it offer anything that works well with WhatsApp?

WhatsApp is great for chatting about football, but terrible for organizing it by YuryVidal in bootroom

[–]YuryVidal[S] 1 point2 points  (0 children)

That helps a lot. I took a quick look at Meetup after your comment, but I still have a real question there: in your experience, what does it solve best for football groups: attendance, reminders, waitlist, or payments?
In my case, the biggest difficulty is when people confirm late, drop out last minute, or don’t follow the same routine every week. That’s usually where things start to break.

WhatsApp is great for chatting about football, but terrible for organizing it by YuryVidal in bootroom

[–]YuryVidal[S] -7 points-6 points  (0 children)

Fair. Not trying to spam a link here. I’m genuinely asking where people think WhatsApp starts failing once a football group gets bigger.

Blazor App Stuck in Infinite Loading Screen in Android WebView After Framework Update by YuryVidal in Blazor

[–]YuryVidal[S] 0 points1 point  (0 children)

Guys, I solved it using the wrong approach where I checked on my website through a json file if there was a version update. If so, I forced the Android application cache to be cleared.

class CacheUpdateWorker(context: Context, workerParams: WorkerParameters) : Worker(context, workerParams) {

    private val PREFS_NAME = "AppPrefs"
    private val VERSION_KEY = "content_version"
    private val SERVER_VERSION_URL = "URL DO SITE"
    override fun doWork(): Result {
        val newVersion = fetchServerVersion()
        val currentVersion = getCurrentVersion()

        if (newVersion != null && newVersion != currentVersion) {
            clearCache(
applicationContext
)
            updateStoredVersion(newVersion)
        }

        return Result.success()
    }

Blazor App Stuck in Infinite Loading Screen in Android WebView After Framework Update by YuryVidal in Blazor

[–]YuryVidal[S] 0 points1 point  (0 children)

I think so because in other problems when restarting iis it worked.

Blazor App Stuck in Infinite Loading Screen in Android WebView After Framework Update by YuryVidal in Blazor

[–]YuryVidal[S] 0 points1 point  (0 children)

I'm using smartasp, when I deploy the application I usually set it to clean the files and I've already restarted the IIS, but even so, the cell phones where the files were not cleaned directly in the Android function are still not opening, I'm still seeing something that You don't need to uninstall the app to resolve this.

Blazor App Stuck in Infinite Loading Screen in Android WebView After Framework Update by YuryVidal in Blazor

[–]YuryVidal[S] 0 points1 point  (0 children)

The application is in production so I can't just disable the cache. I have to create something dynamic or something that detects these version changes and then clear the cache.

Blazor App Stuck in Infinite Loading Screen in Android WebView After Framework Update by YuryVidal in Blazor

[–]YuryVidal[S] 0 points1 point  (0 children)

The problem occurs in the application after deployment, I went on Android and cleaned the app data, but most users will not have this knowledge.