CARVIEW

MOTORHOMES

Select Language

HTTP/2 302 server: nginx date: Tue, 19 Aug 2025 09:46:19 GMT content-type: text/plain; charset=utf-8 content-length: 0 x-archive-redirect-reason: found capture at 20130503045415 location: https://web.archive.org/web/20130503045415/https://programming.oreilly.com/zigurd server-timing: captures_list;dur=0.636684, exclusion.robots;dur=0.024183, exclusion.robots.policy;dur=0.010839, esindex;dur=0.012279, cdx.remote;dur=115.756759, LoadShardBlock;dur=229.892872, PetaboxLoader3.datanode;dur=97.583205, PetaboxLoader3.resolve;dur=78.137435 x-app-server: wwwb-app203 x-ts: 302 x-tr: 369 server-timing: TR;dur=0,Tw;dur=0,Tc;dur=0 set-cookie: wb-p-SERVER=wwwb-app203; path=/ x-location: All x-rl: 0 x-na: 0 x-page-cache: MISS server-timing: MISS x-nid: DigitalOcean referrer-policy: no-referrer-when-downgrade permissions-policy: interest-cohort=() HTTP/2 200 server: nginx date: Tue, 19 Aug 2025 09:46:20 GMT content-type: text/html; charset=UTF-8 x-archive-orig-date: Fri, 03 May 2013 04:54:15 GMT x-archive-orig-server: Apache x-archive-orig-x-powered-by: PHP/5.2.17 x-archive-orig-vary: Cookie,Accept-Encoding,User-Agent x-archive-orig-expires: Thu, 19 Nov 1981 08:52:00 GMT x-archive-orig-cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 x-archive-orig-pragma: no-cache x-archive-orig-x-pingback: https://programming.oreilly.com/xmlrpc.php x-archive-orig-last-modified: Fri, 03 May 2013 04:54:15 GMT x-archive-orig-cache-control: max-age=300, must-revalidate x-archive-orig-connection: close x-archive-guessed-content-type: text/html x-archive-guessed-charset: utf-8 memento-datetime: Fri, 03 May 2013 04:54:15 GMT link: ; rel="original", ; rel="timemap"; type="application/link-format", ; rel="timegate", ; rel="first memento"; datetime="Fri, 03 May 2013 04:54:15 GMT", ; rel="memento"; datetime="Fri, 03 May 2013 04:54:15 GMT", ; rel="next memento"; datetime="Tue, 14 May 2013 03:19:37 GMT", ; rel="last memento"; datetime="Thu, 10 Oct 2013 13:34:24 GMT" content-security-policy: default-src 'self' 'unsafe-eval' 'unsafe-inline' data: blob: archive.org web.archive.org web-static.archive.org wayback-api.archive.org athena.archive.org analytics.archive.org pragma.archivelab.org wwwb-events.archive.org x-archive-src: alexa20130503-55/52_33_20130503045231_crawl100.arc.gz server-timing: captures_list;dur=0.670595, exclusion.robots;dur=0.022981, exclusion.robots.policy;dur=0.010140, esindex;dur=0.011541, cdx.remote;dur=24.321984, LoadShardBlock;dur=314.478295, PetaboxLoader3.datanode;dur=136.807382, PetaboxLoader3.resolve;dur=257.198283, load_resource;dur=239.788476 x-app-server: wwwb-app203 x-ts: 200 x-tr: 636 server-timing: TR;dur=0,Tw;dur=0,Tc;dur=0 x-location: All x-rl: 0 x-na: 0 x-page-cache: MISS server-timing: MISS x-nid: DigitalOcean referrer-policy: no-referrer-when-downgrade permissions-policy: interest-cohort=() content-encoding: gzip Zigurd Mednieks - Programming

Zigurd Mednieks

Zigurd Mednieks is a consultant to leading OEMs, enterprises, and entrepreneurial ventures creating Android-based systems and software. Previously he was Chief Architect at D2 Technologies, a voice-over-IP (VoIP) technology provider. There he lead engineering and product definition work for products that blended communication and social media in purpose-built embedded systems and on the Android platform.

Go Native, Go Big, and Go Deep

Android software development at a crossroads

by Zigurd Mednieks | @zigurd | April 29, 2013

Apps have to get bigger and more ambitious. A key question for the developer community is how do you create big, integrated, multi-functional, configurable apps for the mobile enterprise? Curiously, Facebook is providing some answers by not using HTML5 and not attempting to make a cross-platform app. Go native, go big, and go deep.

Facebook Home is a harbinger of serious mobile apps

Facebook Home has earned positive reviews—in many cases from reviewers who had tired of Facebook and the intrusiveness of Facebook’s privacy policies and practices. Facebook Home is an example of a new kind of Android software development. It spans a variety of functions as a suite of cooperating software. It uses Android’s intent filters, high-level interprocess communication (IPC), shared databases (ContentProvider components) and remote APIs to bond together a software product that replaces many of the standard parts of Android—as they are meant to be replaced.

Facebook Home isn’t some kind of rogue hack, nor is it a “fork” of AOSP, as Kindle Fire is. Facebook Home is a tour de force of correct Android application architecture. It takes over your phone, interface by interface, always playing by the rules, and it does so for justifiable reasons: for putting Facebook’s functionality everywhere you want to perform communications and social media functions.

Going native

Moreover, Facebook Home simply can’t be done on iPhone. iOS has a specific vision of apps that is separate from system software, while Android’s frameworks are the basis of both applications and system software. Facebook Home was built with this difference in mind: It replaces key elements of the Android system user experience. It is a suite of communicating apps. The word “app” doesn’t sufficiently describe it.

Read more…