4 ms·

You do know it is still in preview right? Also I use the web client and it works for me, although have to agree it would be nice if the mobile app had access t

by apapli 10y ago

You do know it is still in preview right? Also I use the web client and it works for me, although have to agree it would be nice if the mobile app had access to some of the tabbed content. What else is wrong with the mobile app from your perspective? Finally, here is the API reference if you want to look at it: https://dev.office.com/microsoft-teams https://dev.office.com/microsoft-teams I am looking forward to when they integrate Flow with Teams. That could make things interesting, given all the 3rd party apps that Flow supports now.

deleted 10y ago
[deleted]
darklajid 10y ago
I know that it is in preview, which is why I'm so upset about the idea of adopting it at this point. Seriously: I'm ranting about this product because it is unfinished and unpolished, but obviously the blame for adopting this thing lies in this company. I wouldn't criticize it that much if I'd be able to watch the painful first steps as a bystander.. You use the web client? I assume you mean teams.microsoft.com? The URL that I see nowhere in my notifications etc? Every notification mail links to a landing page that wants me to download a "native" client (even if none exists for the platform I'm on). Notifications also never include any details: They say "Look, you missed stuff on our service. Come back!" instead of actually.. providing any information. The web client has quite some bugs, a fun one is opening a document (which embeds a 365 viewer, I guess) and resizing the window. Last I checked the document view cannot grow. Lots and lots of issues like that. That API site? Yes, I've seen that. I think last time I checked you had to submit your stuff to let MS decide if it'll be part of a non-existent future "app store" thing. At least for Office365 hosted instances?

4 ms·

You do know it is still in preview right? Also I use the web client and it works for me, although have to agree it would be nice if the mobile app had access t

by apapli 10y ago

deleted 10y ago
[deleted]
darklajid 10y ago
I know that it is in preview, which is why I'm so upset about the idea of adopting it at this point. Seriously: I'm ranting about this product because it is unfinished and unpolished, but obviously the blame for adopting this thing lies in this company. I wouldn't criticize it that much if I'd be able to watch the painful first steps as a bystander.. You use the web client? I assume you mean teams.microsoft.com? The URL that I see nowhere in my notifications etc? Every notification mail links to a landing page that wants me to download a "native" client (even if none exists for the platform I'm on). Notifications also never include any details: They say "Look, you missed stuff on our service. Come back!" instead of actually.. providing any information. The web client has quite some bugs, a fun one is opening a document (which embeds a 365 viewer, I guess) and resizing the window. Last I checked the document view cannot grow. Lots and lots of issues like that. That API site? Yes, I've seen that. I think last time I checked you had to submit your stuff to let MS decide if it'll be part of a non-existent future "app store" thing. At least for Office365 hosted instances?