Posts

Hookflash for Android

hookflash_android_video

 

Today we are shipping our android reference app, sdk and sdk sample app, now in alpha.

Our Hookflash SDK for Android is openly available on Github, today we are releasing a new sample app in code and a Hookflash reference app in the Play Store.

We have run preliminary tests between the iOS app in the iTunes App Store and Android app in the Play Store. Messaging & voice works well, video on iOS has been there for some time now. As you can see from the screenshot video still needs a bit of tweaking on android, as so it has been  temporarily disabled in the reference app.

We are looking forward to working with mobile developers on Android now in addition to iOS. Never has it been so easy to create a scalable mobile messenger with RTC (Real-time Communications) features that other messenger platforms would die for! So come and create something cool! Developers, join up and get started for free today!

Not a developer? No problem, we provide a white label service as well. Send us a note with your project ideas.

Most new mobile messenger apps are tied to age old oligopolies

global_messenger_apps_stats

Name one popular messenger app that has launched in last 2 years that does not ask you for your mobile phone number when signing up. You will be hard pressed to do so. Ok, I might be exaggerating a wee bit but I think you get the point.

If we think about this for a minute it starts to sound a bit odd. New messaging apps mandate that you have a mobile number where you can receive a SMS message so you can join their OTT (Over The Top) community? That’s a bit weird isn’t it? Why not ask them to sign in with identities not tied to a cell phone? Email is certainly more prolific than connected cell phones, right?

So, why is this?

Onboarding is the process used to describe bringing a new user from the discovery process to an active user inside the app/service.

Our smartphone OSs (android, iOS) have made it very easy for devs to take the user’s mobile number and entire address book and upload that to their cloud, which most apps do today. Once in the cloud that data can be used to connect you with others that have done the same thing. Depending on your level of paranoia this can get a bit creepy or you have simply accepted it as the new normal.

To replicate the simplicity of this onboarding process in other forms is not so easy and not near as effective, it would seem.

Other developers defer to the largest social networks as a method for authenticating users, we have done this for our reference apps. Although, there have been plenty of reasons why users may not be interested in signing into your app using their social identity; privacy issues, hijacked accounts to name a couple. Also, why would you as a developer hand over your entire user base to a social network?

Virality is how easily the app spreads through the network.  If the virality of your app hits a point where users are simply adding the app to keep up with their buddies, network effect kicks in, but that generally does not happen for the majority of the apps produced.

SMS messages have a much higher open rate than email and other forms of messaging, for various reasons, which makes SMS a great way to send app invites. It’s also dead easy for the app vendor to enable. If you are on a mobile phone, the dev need not come up with a 3rd party system to send invites, they just use your phone’s own capabilities to send the invites. Less expense for them, open rates increase due to the fact that it looks like its coming from you.

Social messaging has abysmal open rates. Much of the time Social Messages relies on notifications and push messages that are usually ignored or turned off by the user, current company included.

So what options do devs have when creating a messenger app or messenger feature in a app (text messaging, real-time voice or video) where we do not want to rely on phone companies for that initial base of users?

Why not a combination of all the above?

The future lies within federated identity models that allow your users to sign in with whatever ID they prefer and communicate without being pigeon holed into handing over their phone number if they do not feel comfortable doing so.

Developers have their reasons for choosing one ID model versus another, some reasons I have captured in this article. Thankfully, there is no reason to force users into making choices they are not comfortable making. Supporting multiple IDs in a federated model that will allow your LinkedIn authenticated user to communicate with the Phone number authenticated users, exists today.

Imagine a world  where devs can tie custom IDs (your own 3rd party ID model) to social and traditional IDs like phone numbers to electrify a mobile communications paradise. A world where we need not hand the keys of the entire user base over to a social network.

Yep, its real, if you want more information, send us a note we’ll be happy to fill you in.

 

PS. If you feel compelled to weigh in on Net Neutrality and safeguarding the Open Internet, its not too late. Do so here: Email Chairman Tom Wheeler at the FCC, some of the recent comments of the more than 650,000 comments already received.

RTC (Real-time Communications) iOS SDK Update & Hookflash API Pricing

Open Peer - Mobile RTC ToolkitNew releases of Hookflash RTC (real-time communications) mobile toolkits for iOS and Android are now available.

For leading mobile developers, customers and partners; Hookflash mobile toolkits provide an easy, cost effective way to integrate a choice of real-time Text Messaging, High-Quality Voice and Video Chat directly into mobile applications, adding scalable, private, valuable communications functionality for customers and user communities.

“The Hookflash iOS Software Development Kit and accompanying sample app is a stable beta release ready for early customers to integrate into their own apps or to white label.” says Erik Lagerway, Co-founder at Hookflash. “Hookflash Cloud Service beta release is home to more than 275 developers from all across the globe, building interesting and exciting apps ranging from enterprise mobile to banking, gaming and medical applications. I am always excited to hear about how our technology is being leveraged in new ways, it’s what gets me out of bed in the morning!”

Hookflash Mobile Software Development Kits and the Hookflash Cloud Service API are available free of charge (see commercial pricing below) for development, testing and non-commercial purposes (no Credit Card required on signup). If you are a non-profit enterprise organization or recognized charity, contact us, we’d like to help you communicate better for free.

Commercial pricing for the Hookflash Cloud Service API is now also available. See Pricing for details.

Hookflash is setting a new standard in the world of telecommunications; offering API transactional pricing for Voice and Video traffic. Traditionally, until now, Voice and Video calls have been charged on a metered, per minute basis. The Hookflash pricing model provides what leading developers, service providers and enterprise customers expect and require from modern APIs.

At $0 .001 (1/10 of 1 cent) per API call Hookflash enables integrated high quality messaging, voice and video chat for developers and enterprise customers in a way that has not been available until now.

“Hookflash is doing for real-time communications what Amazon Web Services (AWS) has done for Cloud Services, metered minutes are a thing of the past, the future of Real-time Communications is in API services and pricing models that scale” explained Trent Johnsen, CEO.

A Hookflash reference app built on the Hookflash Mobile SDK, “Hookflash Messenger” integrated with Facebook as an example of directory and identity is available in the  iTunes App store here.

A Hookflash Android reference app will follow soon. The Hookflash Android RTC SDK is available now in early beta, with limited documentation.

The previous reference application, “Hookflash for iPad” with LinkedIn directory and identity features has been removed from the iTunes app store to make way for the latest iOS reference application.

Developer sign up: http://fly.hookflash.me
Open Peer RTC iOS toolkit: https://github.com/openpeer/opios
Open Peer RTC Android toolkit (early beta): https://github.com/openpeer/opandroid
Developer documentation: http://docs.hookflash.com

About: Hookflash powers a new generation of integrated, Open, Over-the-Top, Internet messaging, voice and video chat for Mobile and the Web with the new standard for secure signalling and identity; Open Peer.

For additional information please visit Hookflash.com. Follow us on Twitter: @Hookflash.

1-855-Hookflash (466-5352)  or “info@hookflash.com”.