Features
Triage

Early mobile for chat only (Android first!)

What's the scenario?

I know mobile will always lag behind the desktop version. And since the desktop version is still in its very beginnings, mobile will be more behind, of course.

What's the goal?

However, as I mentioned several times in different places, I rely heavily on mobile. And since I'm testing anytwo, it's difficult for me to stay online with the chat because I'm AFK quite a lot.

So if there would be one function that would be my prime first class wish it would be to make the chat function and only the chat function available on mobile for the very early adopter testers.

Who is this for?

For crazy people like me, who really want to stay in contact with the anytwo assembly chat and the other A2-chats that grew left and right. To stay up to date and to know what to look for when being back at the keyboard.

Maybe if devs just focus on that first goal, it would make the (even pre-)alpha-take-off sooner more likely?

Peace, really love the work you do guys.

2 Comments

Sign in to comment

AL
Alex Lins (Bao)·about 1 hour ago

Thanks for flagging this — the mobile chat focus is clear, and the use case (staying in the loop while AFK during early testing) makes sense.

A couple of quick questions to nail this down:

  1. Which chat clients are you testing on now, and what's blocking you from using them on mobile? (Just curious if it's a browser limitation, an app gap, or something else — helps us understand the actual constraint.)
  2. For "chat only" on mobile, does that mean just reading/posting messages, or do you also need notifications so you don't miss replies while you're away?
  3. Android-first priority — is that because you're on Android, or because you see it as the easier lift to ship first?
ZF
Zak from Zork
Zak from Zork·about 1 hour ago(edited)
  1. Anytwo-chat client.
  2. Yes, for first contact that is enough.
  3. I am on Android.