ENTRIES TAGGED "android"

Four short links: 5 December 2013

Four short links: 5 December 2013

R GUI, Drone Regulations, Bitcoin Stats, and Android/iOS Money Shootout

  1. DeducerAn R Graphical User Interface (GUI) for Everyone.
  2. Integration of Civil Unmanned Aircraft Systems (UAS) in the National Airspace System (NAS) Roadmap (PDF, FAA) — first pass at regulatory framework for drones. (via Anil Dash)
  3. Bitcoin Stats — $21MM traded, $15MM of electricity spent mining. Goodness. (via Steve Klabnik)
  4. iOS vs Android Numbers (Luke Wroblewski) — roundup comparing Android to iOS in recent commerce writeups. More Android handsets, but less revenue per download/impression/etc.
Comment: 1

WORA Can Be Better Than Native

Targeting the highest common denominator

Some would claim that native is the best approach, but that looks at existing WORA tools/communities, which mostly target cost saving. In fact, even native Android/iOS tools produce rather bad results without deep platform familiarity. Native is very difficult to properly maintain in the real world and this is easily noticeable by inspecting the difficulties we have with the ports of Codename One, this problem is getting worse rather better as platforms evolve and fragment. E.g. Some devices crash when you take more than one photo in a row, some devices have complex issues with http headers, and many have issues when editing text fields in the “wrong position”.

There are workarounds for everything, but you need to do extensive testing to become aware of the problem in the first place. WORA solutions bring all the workarounds and the “ugly” code into their porting layer, allowing developers to focus on their business logic. This is similar to Spring/Java EE approaches that addressed complexities of application server fragmentation.

Read more…

Comments: 2

Upward Mobility: Microsoft’s Patent Arsenal Is Full of Blanks

Why innovate in the product space, when you can leech money instead?

It is with some amusement that your humble servant read this week of Microsoft’s lucrative business licensing their patents to Android handset makers. How lucrative? Evidently, over two billion dollars a year, five times their revenue from actual mobile products that the company produces. What is harder to discover, unless you do a lot of digging, is what the Android vendors are actually licensing. You have to dig back into the original suit between Microsoft and Motorola to find a list of patents, although they may have added to their portfolio since then through further acquisitions. The thing is that, unlike many parts of the software industry, the cellular portion actually has some valid patents lurking around. Cell phones have radios in them, and there are continual improvements in the protocols and technologies used to make data move faster. As a result, it is a perfectly reasonable assumption to make that Microsoft has acquired some of these cellular patents, and is using them as a revenue stream. Unfortunately, a look at the Motorola suit patent list tells a different story. Read more…

Comment
Four short links: 8 November 2013

Four short links: 8 November 2013

Android Crypto, Behaviour Trees, Complexity Cheatsheet, and Open Source Game Theory

  1. An Empirical Study of Cryptographic Misuse in Android Applications (PDF) We develop program analysis techniques to automatically check programs on the Google Play marketplace, that 10,327 out of 11,748 applications that use cryptographic APIs (88% overall) make at least one mistake.
  2. Introduction to Behaviour Trees — DAGs with codey nodes. Behavior trees replace the often intangible growing mess of state transitions of finite state machines (FSMs) with a more restrictive but also more structured traversal defining approach.
  3. P vs NP Cheat Sheetthe space and time Big-O complexities of common algorithms used in Computer Science.
  4. Game Theory and Network Effects in Open Sourcedelicate balance of incentives go into the decision for companies to Open Source or close source their software in the midst of discussions of Nash Equilibria. Enjoy.
Comments: 5
Four short links: 4 November 2013

Four short links: 4 November 2013

Glass Games, Dopplr Design, Free Android, and Shameful Security

  1. A Game Designer’s Guide to Google Glass (Gamasutra) — nice insight that Glass is shovelware-resistant because input is so different and output so limited. (via Beta Knowledge)
  2. Be Polite, Pertinent, and Pretty (Slideshare) — design principles from Dopplr. (via Matt Jones’s memorial to Dopplr)
  3. Replicant — free software Android. (via Wired)
  4. Femme Fatale Dupes IT Guys at Government Agency (Sophos) — story of how a fake LinkedIn profile for a pretty woman reflects as poorly on security practice as on gender politics.
Comment
Four short links: 30 October 2013

Four short links: 30 October 2013

Offline Javascript, Android Coding, Stats Fails, and Stream Data

  1. Offline.js — Javascript library so web app developers can gracefully deal with users going offline.
  2. Android Guideslots of info on coding for Android.
  3. Statistics Done Wrong — learn from these failure modes. Not medians or means. Modes.
  4. Streaming, Sketching, and Sufficient Statistics (YouTube) — how to process huge data sets as they stream past your CPU (e.g., those produced by sensors). (via Ben Lorica)
Comment
Four short links: 21 October 2013

Four short links: 21 October 2013

Android Control, Privacy Eluded, Design Challenges, and "Watson, What's This Lump?"

  1. Google’s Iron Grip on Android (Ars Technica) — While Google will never go the entire way and completely close Android, the company seems to be doing everything it can to give itself leverage over the existing open source project. And the company’s main method here is to bring more and more apps under the closed source “Google” umbrella.
  2. How to Live Without Being Tracked (Fast Company) — this seems appropriate: she assumes that every phone call she makes and every email she sends will be searchable by the general public at some point in the future. Full of surprises, like To identify tires, which can come in handy if they’re recalled, tire manufacturers insert an RFID tag with a unique code that can be read from about 20 feet away by an RFID reader..
  3. method.acComplete 50 challenges. Each challenge is a small, design related task. They cover theory and practice of one specific design subject. Challenges are progressively more difficult, and completing them gives you access to more intricate challenges.
  4. IBM Watson’s Cancer Moonshot (Venture Beat) — IBM is ready to make a big a bet on Watson, as it did in the 1970s when it invested in the emergence of the mainframe. Watson heralds the emergence of “thinking machines,” which learn by doing and already trump today’s knowledge retrieval machines. I for one welcome the opportunity to be a false negative.
Comment
Four short links: 9 October 2013

Four short links: 9 October 2013

Android Malware Numbers, Open Networking Hardware, Winning with Data, and DIY Pollution Sensor

  1. Android Malware Numbers — (Quartz) less than an estimated 0.001% of app installations on Android are able to evade the system’s multi-layered defenses and cause harm to users, based on Google’s analysis of 1.5B downloads and installs.
  2. Facebook Operations Chief Reveals Open Networking Plan — long interview about OCP’s network project. The specification that we are working on is essentially a switch that behaves like compute. It starts up, it has a BIOS environment to do its diagnostics and testing, and then it will look for an executable and go find an operating system. You point it to an operating system and that tells it how it will behave and what it is going to run. In that model, you can run traditional network operating systems, or you can run Linux-style implementations, you can run OpenFlow if you want. And on top of that, you can build your protocol sets and applications.
  3. How Red Bull Dominates F1 (Quartz) — answer: data, and lots of it.
  4. Ground-Level Air Pollution Sensor (Make) — neat sensor project from Make.
Comments: 3

Upward Mobility: Dear Apple, Please Stop Hogging All the Good Stuff

Forget Touch ID, we're still waiting for access to Siri!

As I mentioned last week, the new Touch ID feature of the iPhone 5S is (at least for the moment) only usable by Apple created software. What this means is that a developer can’t take advantage of the feature to authenticate a user inside an application, it can only be used to unlock the phone and authenticate to iTunes.

This continues a troubling trend we’ve seen with Apple lately. Nearly two years after the release of Siri, the voice UI is still locked out for anyone but Apple and their chosen partners (such as Wolfram Alpha.) I understand that opening up a technology for third party usage takes planning and work, but twice in a row now, Apple has released what could be a transformative technology, and left the developer community out of the picture.

Read more…

Comments: 2
Four short links: 27 August 2013

Four short links: 27 August 2013

Web Broken, Android Ads, Password Cracking, and Adobe Brackets

  1. Bomb in the Garden (Matthew Butterick) — de­sign ex­cel­lence is in­hib­it­ed by two struc­tur­al flaws in the web. First flaw: the web is good at mak­ing in­for­ma­tion free, but ter­ri­ble at mak­ing it ex­pen­sive. So the web has had to rely large­ly on an ad­ver­tis­ing econ­o­my, which is weak­en­ing un­der the strain. Second flaw: the process of adopt­ing and en­forc­ing web stan­dards, as led by the W3C, is hope­less­ly bro­ken. (via Alex Dong)
  2. Google’s New Play Store Policies on Ads (The Next Web) — the walls of civilisation holding back the hordes of assclowns. Imagine the behaviour responsible for each of these restrictions.
  3. Inside Password Cracking (Wired) — how pros go about cracking your password once they have the encrypted hash. (And gosh, how those “but I used numbers and symbols!” passwords fall)
  4. Brackets (Github) — open source web code editor by Adobe.
Comment