What is the difference between using meet.jit.si and JaaS? - jitsi

I am making a video conferencing application using the Jitsi Android SDK.
I may use either the meet.jit.si server as a media gateway to a JaaS (Jitsi as a Service) from 8x8 corporation. What are pros and cons of those?

In very simple words meet.jit.si is for public use for doing video conferencing for personal use, we don't need to host anything to use their app, we can start a person meeting just click of button-like google meet. while JaaS (Jitsi as a Service) from 8x8 is like the PaaS which provides backend microservices to support our self-hosted Jitsi.

Related

Skype for Business WebSDK for On premises environment

We are using Skype for Business 2015 in our Organization (On-premises environment).
We are trying to integrate Skype web features to the Intranet Web sites using Skype for business WebSDK. Internet connectivity/access are not allowed in my environment.
I tried downloading and running sample mentioned in below link.
https://msdn.microsoft.com/en-us/skype/websdk/docs/gettingstarted#sectionSection4
While evaluating I figured out that SkypeBootStrap.min.js is looking for sdk.js hosted in (https://latest-swx.cdn.skype.com/jLync/master_0.4.514/sdk.js)
Can you please suggest any alternate approach for running SkypeWebSDK samples?
My ultimate goal is to develop a reusable client-side component that can be integrated into any of our intranet web applications within our firm which provides all of Skype communication options (including audio, video and screen sharing) through a simple client-side API. What is the best way to achieve this?

Does Bluemix support MBaaS (Mobile Backend as a Service)?

I am reading about and then trying to use IBM Bluemix. I have seen some confusing statement about MBaaS support on Bluemix. Some sites mention that Bluemix is a PaaS, and some places say it supports MBaaS. I have basic doubts: does IBM support MBaaS? If yes, where can I find the full MBaaS features list for IBM Bluemix? I couldn't find it in IBM site.
You're correct: Bluemix is a PaaS. However as you probably know and as you can see here:
Mobile backend as a service (MBaaS) enables you to quickly integrate
your mobile apps with data and functions in security-rich, backend,
cloud storage. MBaaS is usually delivered through a set of custom
software development kits (SDKs) and application programming
interfaces (APIs). MBaaS can offer you full data synchronization, user
management, push notifications, integration with social networking
services, and file-handling.
A PaaS provides SDKs and APIs and for this reason it can support MBaaS. In Bluemix the MBaaS capabilities are provided by the MobileFirst platform. It is designed for building and enhancing multiplatform, enterprise-grade apps that can be native or hybrid – for Android, iOS, and Windows. You can get started here.
Yes, Bluemix Mobile supports a Mobile Backend as a Service.
Here are the current services that we have that support the MBaaS pattern and a bit of information about them (and here's a quick graphical view and some links for how to get started):
Mobile Client Access
This service enables you to secure your Mobile Application. You can add Facebook, Google, or custom authentication to your application.
Push Notifications
You can add the Push Notifications service to send push notifications to your app on Android and iOS.
Mobile Analytics (Beta)
The Mobile Analytics service enables you to gather crash and usage knowlege about customers using your mobile app.
Cloudant NoSQL DB
The Cloudant service is the IBM NoSQL database to store your data.
Object Storage
The Object Storage service is an unstructured cloud data store where you can store things like images or files.
Mobile Foundation
The catalog also includes the Mobile Foundation service which you can use to create a test environment before deploying or purchasing the on-premise software. This service is another way for enabling a developer to create a mobile channel.
You may have a look at this :
http://www.ibm.com/mobilefirst/mobile-backend-as-a-service/mbaas.html

IBM worklight for developing static websites

I am new to Worklight and am currently doing proof of concepts to understand the features and strengths of the platform to create mobile web apps, hybrid apps and native apps.
Can IBM Worklight also be used for developing static information websites for multiple mobile devices?
Even if all you want to do is serve dynamic content form your server to the mobile device there are some advantages to use Worklight, for example by wrapping your site in a hybrid shell you can gain the presence in application stores (Apple iTunes and Google Play).
You can check "Module 45.1 – Worklight App as a Container For Server Generated Pages" ftp://public.dhe.ibm.com/software/mobile-solutions/worklight/docs/v505/Module_45_1_-_Worklight_App_as_a_Container_for_Server_Generated_Pages.pdf for more information about how to do it.
If you will not use your static site as the resource of the content but will use the Worklight application you will have a few advantages
1) Will work offline
2) Faster response time (no round trips (HTTP requests) to get the whole HTML, CSS, JavaScript, images)
At the end of the day Worklight application are for applications, where there is a interaction between backends and the client and usage of device capabilities (like location, camera, etc.) and not only static content.
Can it be used to create static sites? Yes. Is that a good use of the software license? Probably not. There is a lot more power in Worklight than just creating a static site. I would suggest really understanding responsive web design and using that to create your mobile friendly sites.

Can I create a Hangout "client" program? (kind of Google TalkAbout)

As stated in the Google Talk for Developers site, you can use the provided APIs to build a client that connects to the Google Talk service.
I would like to know if it's possible (or it will be in the near future) to build a similar client to the google hangouts.
What we pretend is to build something similar to cloud print, that provides printing services to the cloud, but for audio/video streaming: a camera and microphone would replace the
printer.
Thanks a lot.
Talk and all the XMPP stuff is going to be put down soon.
The new Hangouts infrastructure is proprietary. It only has API to integrate Hangouts into web pages and applications, but no API or protocol to create an alternative Hangouts client software.
https://github.com/tdryer/hangups is a library that does exactly that, with a command-line client for Linux.
https://github.com/xmikos/qhangups is a PyQt-based cross-platform app that aims to provide an open-source alternative to the Chrome-based official desktop app. Unfortunately it's not working at the time of posting, but the author is investigating the issue.

Browser <-> Client Hardware API?

Are there any initiatives to implement/agree upon a standard API for connectivity between web browsers and client hardware.
Example: The iPhone has a GPS/Camera/Accellerometer in it. It'd be very cool if my web app could communicate with them (rather than me having to write a thick ObjectiveC application).
The closest thing I've seen to that is the Android phone API, which lets your programs access its hardware (relatively) painlessly. Google's pushing for it to become the new standard, but its hardly the same thing as a web-app (which, by most definitions, runs entirely in your browser?).
The upcoming version of FireFox has an API to read your lat/long off a GPS device.
To add to my own question; Yahoo provides a geolocation service called FireEagle that could act as a mediator and provide similar functionality.
In essence the phone communicates with a central Yahoo server updating its location. Your web app can then determine your approx location from that central server.