I noticed in the commercial API you have the ability to use branded map skins. How is that actually implemented on the app side? Are there "MapView" objects exposed? The commercial API documentation is not available online, but I would love to read it before I commit to purchasing a contract. I'm really interested in what is exposed by the REST Api also.
Glympse map branding is currently available only in the HTML-based Glympse viewer (i.e. a customizable experience for invite recipients or when viewing a Glympse group). There are a number of themable components, most of which are available with any registered Glympse app.
Unfortunately, the customizable map experience on the app side of things has not yet been released.
Related
I would like a Teams user to video call an other Teams user using external hardware (usb camera) and using mobile devices (android first).
What can Teams apps do?
...
Collaborate on items in external systems. One of the core scenarios
for a custom Teams app is to bring information or items into Teams
from some other place, and have a conversation around it. You can push
information into Teams, enable your users to search for and pull it on
demand, or make it available in an embedded web view.
Source
I guess I could develop a small web application and a server which could act as a bridge.
Android app streams a video to my webserver, teams web app loads video stream from my server. Could that work?
I've found some other people asking similar things, and they did not get an answer.
https://techcommunity.microsoft.com/t5/Microsoft-Teams/SDK-for-Microsoft-Teams/m-p/261008
The easiest would be, if teams had a real sdk, but it seems to me, that it only has support for very limited "plugins".
Currently This is not supported in Teams.
I have a desktop app to which I want to integrate Microsoft Teams.
Does Teams provides an API for the integration.I read few articles but they all explained how to create apps in Teams and use of Microsoft Graph API to get information about Teams/channel etc.
Could someone help me with this, if they had any solution.
few of my finding on the internet:
https://blog.thoughtstuff.co.uk/2017/04/microsoft-actively-working-on-a-teams-api/
https://developer.microsoft.com/en-us/graph/graph-explorer#
https://microsoftteams.uservoice.com/forums/555103-public/suggestions/16972258-developer-api-to-read-create-teams-and-channels-in?page=2&per_page=20
There are two distinct ways of accomplishing this:
Using the Microsoft Graph API to create/read/write information. Currently the only thing we support is the ability to add a team to an existing Office 365 Group, the ability to create and read channels within a Team, and to post a message to a team/channel. We are adding more APIs, including the ability to read messages from a channel, but it's not available yet (and we don't have a public ETA). The ability to read and write channel messages from a channel should allow you do what you want.
Controls that you can embed in an application that read/write the data for you. That's a common developer request and we will deliver that eventually, but it's further out.
I am looking to create a bot and have come across Microsoft Bot Framework (with LUIS or can use C# SDK provided by API.AI) and Howdy.ai Botkit (with Middleware support for LUIS & API.AI).
Can someone help me with comparison between these two?
I am looking for following things in my bot -
Support multiple channels including Email.
Have the bot act in both reactive (reply to some user message) and proactive (send out message to users once a day about something important to them or followups)
manners.
Save and later retrieve user provided data (manage state).
Rich message support.
Respond with delay.
Manage conversation history.
Are there things that are available in one but not in another?
I tried developing a bot in Botkit and MS Bot framework both. Ultimately I went with MS bot framework. Some of my reasons which could help with the comparison:
MSBotFramework has support for skype, slack, telegram, Facebook, and many other channels. BotKit, the last I checked, supported only Facebook and slack. I was targeting skype and telegram and that was a deal breaker.
Botkit currently is node.js only. On the other hand, MSBotFramework has .Net, Node.js and even a REST API (which basically means you can use it from any language you want). Also, there are python wrappers available which internally make use of the REST API.
Being a Microsoft product, MSBotFramework's integration with skype, azure, azure analytics, LUIS and other Microsoft services is very easy. This could be required for developing, deploying or integrating natural language support. Botkit supports LUIS integration, which is fairly easy( maybe as easy as MSBotFramework). The analytics (through botkit studio) (was) very basic and MSBotFramework wins hands down here.
I found the documentation for MSBotFramework more comprehensive than Botkit but both of them have an equal amount of resources and documentation.
Some of the other points you have asked about:
Proactive messages depend on the channel you are developing for. For eg. Facebook allows a time window of 24 hours from the user's last message in which you can reply. Whereas other platforms like skype and telegram allow you to send a message anytime you want.
State management will need to be handled on your end. Bot Framework provides some mechanism, but it is not robust enough to be used in production.msdoc
Rich messages are platform dependent, but bot framework does pretty well in catering to most of them. So, the way this works is, you send back the message to bot framework in its own rich message format. It converts to platform specific format. If you have only one or 2 platforms in mind, you can develop accordingly.
Respond with delay - You will have to implement it yourself, though bot framework has lots of examples of doing this.github
Managing conversation can be done easily if you are using C# and .Net platform in general. The documentation and number of examples are very impressive.github repo for samples
All in all, I would recommend MS bot framework.
layer vs quickblox , which is better(easier to implement,performance features)
for messages,voip, and video chat,
and do I need to add parse.com with those messaging solutions for content storage.
Some of the differentiating points are:
Quickblox supports video and audio calling, layer doesn't.
Layer provides SDK for iOS, android and Javascript & unity sdk are in queue. Quickblox provides sdk for iOS, android and js.
All the above mentioned are only for client. If you want to control something from your server then you have to use Rest APIs.
Layer provides Rest and Websocket API but Quickblox only provides rest API.
Quickblox states that their js sdk can be used on node.js server. But I was getting This browser not supported error in connecting to chat from node.js server. The same error is also specified here. This means that there is not way to get real time notification on new message/user on your server with Quickblox.
Quickblox free tier customer support sucks (for eg. see here (no response on any ticket), here and here). I found Layer's support very good.
Layer's documentation is too good. Quickblox's is confusing. Also quickblox have no doc describing there basic concepts.
Layer also provides support for UIKs.
Quickblox provides in house user management, layer does not. But you can use Parse to do that as defined in layer docs.
Layer has platform API to bulk and system level actions like sending announcements and they also provide engagement analytics on those.
I also find this small layer's feature very useful.
There are many more differences. I just started using chat Baas last week. Will update the answer with time.
I was wondering if it is possible to develop a text messaging kind of application similar to WhatsApp, but for between WP7 devices? What difficulty programming skill level am I looking at and what would be required to develop such an app? Thanks!
In general I don't think it will be really difficult to build an app like WhatsApp. (Although I only heard about the funcationality) So I will give you the information I think you should have at a minimum.
In the first place you need your WP7 app, which I think should have push notifications to notify users about new messages. (Note: push notifications work in batches, so there will be no instant delivery notification to the end user.) You should have a login system in your WP7 app, which makes users uniquely identifiable.
Somewhere you should have a central datastore where you can store users, messages, relations between messages (replies, forwards, etc.) (Note: If your app becomes as big as WhatsApp you should have a really good scalable datastore.).
I would use WCF to communicate between your datastore and the WP7 app. Probably I have overseen something right now, but this will give you a start for defining your applications architecture.
UPDATE 12:54
As i saw your comment about where to start I searched for some documentation:
There is a free e-book from Charles Petzold which covers alot:
http://www.charlespetzold.com/phone/
Also there are a lot of code samples and documentation on MSDN:
Main overview of WP7 development:
http://msdn.microsoft.com/en-us/library/ff402535(v=vs.92).aspx
WP7 code samples:
http://msdn.microsoft.com/en-us/library/ff431744(v=vs.92).aspx
You can have a look at the Sockets Support section, which may help you to get started.