Today, I’m going to be at DLD TLV – if you are around…
Please come to say hello.
If you wish to read the background on RESTful APIs It’s all started here. You can look at some good examples for RESTful APIs from Google, Twitter and many others. In this post, I will try to focus on some important aspect that you want to keep in mind when you are building your next RESTful API. Btw, if you are looking on an efficient way to create it – Checkout my talk from last Google I/O. It’s over a year now, but still very relevant.
In the past, I gave few presentations on ‘Modern web apps‘ and each time I tried to show compelling examples.
Here is a new source (mobile web apps ftw) that might help you see what can be done (today) on the mobile web.
Few good examples to checkout:
Another good site to get insperation is: mobile-patterns.com
If you have other great suggestions – please use the comments and I’ll add them.
Great news for the mobile web.
As Opera jump on Blink few months ago, it will be great to have this powerful engine on Microsoft phones as well.
Originally posted on Gigaom:
Opera has inked another deal with Microsoft – after Opera’s full-fat mobile product became the default browser on the Nokia X2 Android handset, Opera Mini will now be the default on Microsoft’s feature phones on the Asha, Series 30+ and Series 40 platforms.
The eagle-eyed among you will have spotted a slightly limiting factor in all this: [company]Microsoft[/company] is killing off almost all of these devices — extremely low-end Series 30+ devices like the newly-launched Nokia 130 may survive a while longer — in a push to take Windows Phone towards the bottom of the market.
But it will be a slow death, over the next year and a half or so, and Opera will be there for their twilight, gently shoving the currently-default Xpress Browser to the side.
“Users will begin to receive notifications on their phone starting October 2014, providing them with information on how to upgrade from…
View original 97 more words
In this tutorial, we will go over the simple steps to install an IPSec/L2TP VPN server on google compute engine.
There are many cases that we need to use a secure channel between a local machine (it might be the firewall of our office or just your development laptop) and our cloud infrastructure. The answer (in most cases) is to have a VPN server in our cloud that will be the entry point. Here we are going to look at a client-server solution. If you are looking at a solution that will give you server to server configuration please go to this post: greenido.wordpress.com/2014/04/10/how-to-set-a-vpn-on-google-compute-engine/
First, I’m going to assume you have an account with Google cloud and you already know how to launch an instance on Google Compute Engine. If not, this post could help you do it in less then 5 min.
There are cases were you wish to collect statistics on your youtube videos or channel. There are few options to do it with YouTube API. As the API support many languages you can choose the one that will work for your environment. In many of these options, you will need to develop a server side that will fetch the data and a front-end to present it and give the users option to query it. If you wish to dive deeper (e.g. specific metric on channel performance and videos statistics), you will need to work with YouTube Analytics API.
In this post, we will see a simple example to create a dashboard that will be updated on a daily bases. Since we wish to save ourselves from building (and maintaining!) a server side and a web app to access it, we will use the power of Google Apps Script (GAS) and Google sheets.