Curated for content, computing, data, information, and digital experience professionals

Category: Internet & platforms (Page 6 of 8)

Multi-channel Publishing and Content Reuse

We’re big believers in the potential for learning from colleagues in other industries. There are many shared challenges crossing vertical boundaries not always obvious because of different vocabularies, and often a gem can be found in the variety of solutions, or an idea can be sparked by a slightly different lens on the problem. The publishing industry’s influence on computing and digital experiences goes way back and is especially applicable horizontally – markup languages, style sheets, electronic type – and of course multi-channel publishing. This is why we have usually included a publishing track in our conferences. This session looks at how a couple of publishers have dealt with some thorny multichannel publishing issues.

P2. Multi-channel Publishing and Content Reuse

Tuesday, December, 3: 2:40 p.m. – 3:50 p.m.

In this session two publishing organizations report on projects that involve moving publications and existing content from print to multi-channel digital. Business Insurance, part of Crain Communications, implemented a digital publishing strategy that supports interactive digital content and content reuse across print, Web, iOS, and Android, all based on HTML5. Wolters Kluwer Health now creates textbooks with versions for print, multiple eBook formats, and integration with Learning Management Systems and other advanced learning tools. As part of their multi year initiative they report on a recent project where they implemented round tripping between XML and author-editable Word documents, and discusses the technical and organizational problems they solved.

Moderator:
Tom Brown, VP, Multichannel Solutions, HP

Speakers:
Dave White, Chief Technology Officer, Quark Software Inc.
Case Study: Transforming Print Content into Mobile and Web Apps
Ken Golkin, Technical Project Manager, Wolters Kluwer Health
and
Niels Nielsen, Managing Director, Avalon Consulting, LLC
Long Cycle Reuse in Textbook Publishing: Cracking the XML–>Word–>XML Round Trip Nut

 

Content and User Experience Design for the Internet of Smart Things – Gilbane Conference Spotlight

There are many reasons to be excited about the Internet of Things, a content channel is not usually considered one of them. In fact, the mere suggestion of a need to support one more digital channel is enough to cause many execs to consider a career change, never mind n additional channels, and n is the future.

Many internet things don’t and won’t need to prepare content for direct human consumption, but many will – cars and watches and glasses are just the beginning. The variety of form factors, display technologies, and application requirements will present challenges in user experience design, content strategies, content management and data integration. The session we are spotlighting today will focus on the user experience design challenges, of which there are many.

T7. Have You Talked To Your Refrigerator Today? Content and User Experience Design for the Internet of Smart Things

Wednesday, December, 4: 2:00 p.m. – 3:20 p.m. – The Westin Boston Waterfront

The web is dead. Or is it evolving into the Internet of things? If so, how can we harness the emergence of smart and app-enabled devices, appliances, homes, cars and offices into the digital gene pool? Four senior executives in experience planning and strategy, technology, creative and user experience will provide a point of view on the Internet of smart things and answer key questions, including the following, using real world examples:

  • How can your smart washing machine, refrigerator and dishwasher be mated with intelligent apps, CRM, and dynamic content management systems to create real-time marketing and ecommerce experiences?
  • What happens to content strategy and management as app-enabled “playthings” become essential to your work and family life?
  • What do we do as video baby monitors become digital caretaking, developmental tracking, medical monitoring, and product ordering parent-bots?
  • What is the optimal customer experience for using voice to simultaneously integrate and operate your car, your mechanic, your GPS, your iPod, your radio, your tablet and your smartphone?
  • What best practices are needed for creative designers, content strategists, marketers, and user experience designers to create engaging Internet of smart things experiences?
Moderator:
Doug Bolin, Associate Director, User Experience Design, Digitas
Panelists:
Michael Vessella, Vice President, Director, Experience Design, Digitas
Michael Daitch, Vice President, Group Creative Director, Digitas
Adam Buhler, Vice President, Creative Technology / Labs / Mobile, Digitas

 

Mobile development strategy – platform decision update

Last April I suggested that evolving mobile platform market changes meant organizations needed to re-visit their mobile development strategy and said

“What has changed? To over simplify: Apple’s dominance continues to increase and is unassailable in tablets; RIM is not a contender; Microsoft is looking like an up-and-comer; and most surprising to many, Android is looking iffy and is a flop in tablets with the exception of the very Amazon-ized version in the Kindle Fire.”

Not surprisingly, things have changed again. Two major changes are that Samsung is now a major player, and Google has finally made progress in tablets with the Nexus 7 and the much improved Android “Jelly Bean” release. Amazon’s second Fire is also more robust. There are now real choices in tablets – personally I have an iPad, a Fire HD, and a Nexus 7, and I use all three of them, and for many purposes I just grab the closest. But businesses making a significant investment in a platform for development need to carefully evaluate its stability and staying power.

One thing that hasn’t changed is the debate among analysts over what the iOS and Android market share numbers mean – specifically, whether the larger and accelerating Android market share numbers threaten Apple’s dominance. At first glance it is natural to think that dominant market share signifies a safer bet, and indeed many analysts make this point. But it’s not so simple. Last year there was evidence that even though Android devices had a market share advantage, Apple devices accounted for much more total online activity – were used more – and it is probably safe to say that use is a requirement of product success.

More importantly, if you look at profit share, Apple continues to dominate. So the opposing view is that Apple may be the safer bet since for most values of company/product health, profit trumps revenue.

In “The Mobile Train Has Left The Windows 8 Platform Behind“, John Kirk, who doesn’t mince words, has no patience for the view that Android’s market share means it will squash Apple:

“According to Canaccord Genuity, Apple took in 69% of the handset (all mobile phones, not just smartphones) profits in 2012. Samsung took in 34%, HTC accounted for 1%…

No one not named Apple or Samsung is making any meaningful profits from the handset sector…

Many industry observers have the handset market all wrong. They opine that Andoid is destroying iOS. What is actually happening is:

  1. With 69% of the profits, iOS is doing just fine. More than fine, actually.
  2. Android destroyed every phone manufacturer not named Apple (BlackBerry, Nokia, Palm, etc.).
  3. Samsung destroyed every Android phone manufacturer not named Samsung (HTC, Motorola, Sony Erricson, etc.).

Pundits like to predict the imminent demise of iOS, but those profit numbers say just the opposite. And even as Android’s market share has increased, iOS’s profit share has increased too. Market share is no guarantor of profits. This should be self-evident. But apparently, it’s not.”

Kirk follows up with more entertaining disdain for the “church of market share” at “Does the Rise of Android’s Market Share Mean the End of Apple’s Profits?“.

In terms of tablet market share,

“According to Canalys, Apple – despite being supply constrained – sold 22.9 million tablets for 49% share, Samsung shipped 7.6 million tablets, Amazon shipped 4.6 million tablets for 18% share, and Google’s Nexus 7 and 10, combined, shipped 2.6 million tablets.”

In conclusion,

“Only Samsung and Apple are competing in phones. Only Amazon, Google, Samsung and Apple are effectively competing in tablets. The mobile “train” has left the station and companies like HP, Lenovo, Dell and Microsoft are standing on the Windows 8 platform, watching it pull away.”

For more on Microsoft see Kirk’s full post.

Mobile platforms are still evolving and the coming proliferation of new device types guarantee that there will be continuous and substantial change made to those that survive. No one responsible for a mobile development strategy should wait almost a year to evaluate their current plan. Fortunately there is no shortage of useful platform data. It just needs to be interpreted critically.

How long does it take to develop a mobile app?

We have covered and written about the issues enterprises need to consider when planning to develop a mobile app, especially on choosing between native apps, mobile web apps (HTML5, etc.), or a hybrid approach that includes elements of each. And have discussed some of the choices / factors that would have an effect on the time required to bring an app to market, but made no attempt to advise or speculate on how long it should take to “develop a mobile app”. This is not a question with a straightforward answer as any software development manager will tell you.

There are many reasons estimating app development time is difficult, but there are also items outside of actual coding that need to be accounted for. For example, a key factor often not considered in measuring app development is the time involved to train or hire for skills. Since most organizations already have experience with standards such as HTML and CSS developing mobile web apps should be, ceteris paribus, less costly and quicker than developing a native app. This is especially true when the app needs to run on multiple devices with different APIs using different programing languages on multiple mobile (and possibly forked) operating systems. But there are often appealing device features that require native code expertise, and even using a mobile development framework which deals with most of this complexity requires learning something new.

App development schedules can also be at the mercy of app store approvals and not-always-predictable operating system updates.

As unlikely as it is to come up with a meaningful answer to the catchy (and borrowed) title of this post, executives need good estimates of the time and effort in developing specific mobile apps. But experience in developing mobile apps is still slim in many organizations and more non-technical managers are now involved in approving and paying for app development. So even limited information on length of effort can provide useful data points.

I found the survey that informed the Visual.ly infographic below via ReadWrite at How Long Does It Take To Build A Native Mobile App? [InfoGraphic]). It involved 100 iOS, Android and HTML5 app developers and was done by market research service AYTM for Kinvey, provider of a cloud backend platform for app developers.

Their finding? Developing an iOS or Android app takes 18 weeks. I didn’t see the survey questions so don’t know whether whether 18 weeks was an average of actual developments, opinions on what it should take, or something else.

Of course there are simple apps that can be created in a few days and some that will take much longer, but in either case the level of effort is almost always underestimated. Even with all the unanswered questions about resources etc., the infographic raises, the 18 week finding may helpfully temper somebody’s overly optimistic expectations.

 

Tablets in the Enterprise and BYOD strategies

A couple of observations about tablets in the enterprise:

  • Tablets of all dimensions have a role in enterprise use, as do all types of personal computing devices.
  • BYOD is certainly a challenge for some organizations, but is a reminder of how we should have been managing data all along.

Tablets and other personal computing devices in the enterprise
One reaction to Apple’s iPad mini last week was that it would change the dynamic of Apple’s market for tablets since a 7″ inch tablet is more appropriate for consumers so enterprises would stick to the 10″ versions. The only thing correct about this view is that the tablet market will change. But we don’t know how – use-cases are evolving and there are way too many variables beyond physical size. It seems just as likely that the iPad mini form-factor could grow faster in enterprises than the full size iPad. In any case there are certainly enterprise use cases for a smaller, cheaper iPad, especially since those seem to be the only significant differences, and there is no apparent app development cost or learning curve further easing enterprise adoption.

But the bigger point is that enterprises need to be able to support not only multiple tablet and smartphone form factors but a large subset of an unpredictably large set of personal device types.

This is not a new challenge, it is simply one that is accelerating because of the decreasing costs and increasing ease of device development. “Personal” devices in enterprises are not new – employees have often used their own personal computers especially as they shrunk in cost and to BYOD notebook size. Tablets and phones are the next step, but enterprises will soon be dealing with watches, wearable computing, and implants which is why…

BYOD strategies need to focus on the data not the devices
The BYOD continuum is also largely additive – employees aren’t just replacing devices but often using multiple devices to access and process much of the same data – keeping up with the variety and volume and versions of personal devices is hopeless. A BYOD management strategy that focuses on device management will at best have a negative impact on productivity, will certainly increase costs, and most likely fail. There are environments and applications where data security is critical enough to warrant the overhead of a device management strategy that approaches being fail-proof, but even in these cases the focus should be on the data itself with device control as a backup where it makes sense.

It may not be much easier to manage the data independently but that’s the ball to keep your eye on.

Tablet market evolution and mobile development strategies

It was only about a year ago that the tablet market was only really about general-purpose tablets. There was the dominant iPad, and the fragmented Android market. Ebook readers were a separate animal altogether, although the anticipated release of the first Kindle Fire raised the question of whether it would bridge the general-purpose and ebook market.

In some ways it did, adding enough apps and internet access that it was hard not to sneak in some work email or web research even when your laptop or iPad was purposely left at home for the weekend away with the family. But of course Amazon’s business model was/is different – a subsidized device to increase the sale of content. And Amazon’s use of Android was significantly more customized than other Android tablets.

The folks over at Tech.pinions continue to be a must-read for anyone following/investing in the tablet market. John Kirk in Battle of The Tablet Business Models: Lessons Learned and a Look Ahead, argues that the future of the tablet model will be determined by the business models behind them, and points out some consistencies and lack thereof between the major players, Apple, Amazon, Google, Samsung and Microsoft. He is surely right that too often commentators and analysts have focused on hardware characteristics and software and not paid enough attention to business models. However, product capabilities can either create new business model possibilities or prevent their success so also help determine the landscape. For example, a non-glare, color display with low power requirements that combines the best of an iPad and a Kindle will certainly have a material effect on the market. In any case John’s post contains a number of nuggets.

Another aspect to consider in tablet market evolution is the difference between enterprise and consumer tablet markets. We’ll look at that in another post.

Gilbane Conference workshops

In case you missed it last week while on vacation the Gilbane Conference workshop schedule and descriptions were posted. The half-day workshops tale place at the Intercontinental Boston Waterfront Hotel on Tuesday, November 27, 9:00 am to 4:00 pm:

  • Insider’s Guide to Selecting WCM Technology – Tony Byrne & Irina Guseva, Real Story Group
  • Implementing Systems of Engagement: Making it Work with the Team That Will Make it Work – Scott Liewehr & Rob Rose, Digital Clarity Group
  • So You Want to Build a Mobile Content App? – Jonny Kaldor, Kaldor Group (creators of Pugpig)
  • Content Migrations: A Field Guide – Deane Barker, Blend Interactive & David Hobbs, David Hobbs Consulting
  • Social Media: Creating a Voice & Personality for Your Brand – AJ Gerritson, 451 Marketing
  • Text Analytics for Semantic Applications – Tom Reamy, KAPS Group

Save the date and check http://gilbaneboston.com for further information about the main conference schedule & conference program as they become available.

Time to re-check your mobile development strategy

The mobile platform landscape has changed dramatically in the last few months. So much so that organizations who even recently reached decisions on a mobile development strategy should re-visit their decisions. I’m not talking about HTML5 vs app development issues – though those decisions are just as important and directly related because of continued innovation in device and operating system capabilities combined with the need to protect content development and management investments – but about which platforms will be viable, or meet your level of risk tolerance.

What has changed? To over simplify: Apple’s dominance continues to increase and is unassailable in tablets; RIM is not a contender; Microsoft is looking like an up-and-comer; and most surprising to many, Android is looking iffy and is a flop in tablets with the exception of the very Amazon-ized version in the Kindle Fire. These are pretty general statements, but if you are in charge of your company’s mobile development strategy considering their impact is a good place to start a check-up for a possible course correction.

Another place to start is to read the excellent post by Tim Bajarin Why Google Will Use Motorola To Become Vertically Integrated. I won’t summarize because the entire post and the comments are really a must-read.

« Older posts Newer posts »

© 2025 The Gilbane Advisor

Theme by Anders NorenUp ↑