Group items tagged

Good interview with Charles Jolley - SproutCore - WebKit (met Charles at Web 2.0).  He has left Apple and started a SproutCore Web App development company called "Strobe".  Looking very good Charles! The Blended Brew Apps have become a preferred way of accessing information on mobile devices. But developers want to provide a unified experience, and that is why Jolley believes that we will soon have apps that use HTML5 inside a native app wrapper. "People are looking for an either/or solution, but it is not going to end up like that," he said. Think of Strobe's offerings as a way to create an experience that is a blend of HTML5 and native mobile apps. How this works is that an application is developed in HTML5 instead of proprietary formats. It is wrapped in a native app wrapper for, say, the iPhone, but when accessed through a web browser on a PC or any other device, like tablet, it offers the same user experience. This is a good way to solve a problem that is only going to get compounded many fold as multiple endpoints for content start to emerge. The co-existence of web and native apps also means content publishers need to think differently about content and how it is offered to consumers. The multiplicity of endpoints (iPhone, iPad, TV and PC) is going to force content producers to think differently about how they build the user experiences for different sets of screens. Jolley argues that the best way to do so is to stop taking a document-centric view that is part of the PC-era. In the touch-based mobile device era, folks need to think of ways to have a single technology stack married to the ability to create unique experiences for different devices. And if you do that, there is no doubt that HTML5 and native apps can live in harmony.

When it comes to presenting graphically oriented programs through a browser, the usual go-to development platforms have been Adobe Flash and -- to a lesser extent -- Microsoft Silverlight. But other, more open technologies are starting to show promise. The 10 best Chrome extensions for work and play |Watch a slideshow of this review. That's what Google aims to highlight on Chrome Experiments, a Web site that showcases JavaScript programs that deliver a rich user-graphics experience. Of the nearly 80 projects featured on Chrome Experiments, the majority are graphic demos. As impressive as such eye candy is, they're not good examples of how capable JavaScript can be for running graphically-oriented applications that are actually useful. But there are a few notable ones, which we present here. (Despite the site's name, these programs should run on any browser that supports JavaScript.)

"FREQUENTLY ASKED QUESTIONS What is WhiteHat Aviator? WhiteHat Aviator; is the most secure , most private Web browser available anywhere. By default, it provides an easy way to bank, shop, and use social networks while stopping viruses from infecting computers, preventing accounts from being hacked, and blocking advertisers from invisibly spying on every click. Why do I need a secure Web browser? According to CA Technologies, 84 percent of hacker attacks in 2009 took advantage of vulnerabilities in Web browsers. Similarly, Symantec found that four of the top five vulnerabilities being exploited were client-side vulnerabilities that were frequently targeted by Web-based attacks. The fact is, that when you visit any website you run the risk of having your surfing history, passwords, real name, workplace, home address, phone number, email, gender, political affiliation, sexual preferences, income bracket, education level, and medical history stolen - and your computer infected with viruses. Sadly, this happens on millions of websites every day. Before you have any chance at protecting yourself, other browsers force you to follow complicated how-to guides, modify settings that only serve advertising empires and install obscure third-party software. What makes WhiteHat Aviator so secure? WhiteHat Aviator; is built on Chromium, the same open-source foundation used by Google Chrome. Chromium has several unique, powerful security features. One is a "sandbox" that prevents websites from stealing files off your computer or infecting it with viruses. As good as Chromium is, we went much further to create the safest online experience possible. WhiteHat Aviator comes ready-to-go with hardened security and privacy settings, giving hackers less to work with. And our browser downloads to you - without any hidden user-tracking functionality. Our default search engine is DuckDuckGo - not Google, which logs your activity. For good measure, Aviator integrates Disconnect

Add this to the Sports Illustrated "immersive" magzine for the iPAD as clear indication that the entire idea of what a visual document is has changed dramatically.  Radically. excerpt: The coolest media experiences that I've seen on the iPad - Operation Ajax, a graphic novel created specifically for the device. At the time, the idea was still very much in development, but today the Operation Ajax application has gone live in Apple's App Store. The major startups in digital comics, ComiXology and Graphic.ly, have focused their energies on making deals with publishers to transfer existing comics to the iPad or other devices. Operation Ajax, on the other hand, was created with the iPad in mind, avoiding some of the issues that come with transferring from print (the iPad screen is slightly smaller than a standard comic book page, for starters), and also making the supplementary material that can't be delivered in print a natural extension of the experience.

excerpt: In China, the red-hot tech scene seems dominated by a small group of entrepreneurs who paid their dues in Silicon Valley before returning home to create successful Internet and software startups. Aside from finding fame and fortune, these "returnees" are also laying the foundation for a startup culture that will allow grassroots entrepreneurs to flourish as well. Returnees - Chinese nationals who studied or worked the U.S. - head up just 3 percent of all tech companies in China, yet they represent nearly 70 percent of all startups that go public in the U.S. market (still the largest measure of success in the industry), according to an internal study by Palo Alto, Calif.-based venture capital firm GSR Ventures, which deals exclusively in China. The firm also found startups created by returnees were much likelier to become financially successful and hire more employees than startups founded by Chinese entrepreneurs who never worked in the U.S. Part of that may be cultural: a culture Jack Jia, a partner at GSR sees changing, albeit slowly. he still sees a "drastic" disparity between startups founded by home-grown entrepreneurs and their returnee counterparts during pitching sessions and business plan competitions all across China. Thus, he rarely funds companies headed up by Chinese engineers without managerial-level experience at tech companies in the U.S., even though he would like to encourage the growth of Chinese entrepreneurs who have stayed at home. "Most have no clue what they are doing. The basic expertise, the passion and experience is often lacking," he said. "And it's not that they don't have the same talent or ability, it's just they haven't been exposed to the same things as their American counterparts."

Great chart and HTM5 App development advice from pinch/zoom developer Brian Fling!   excerpt: In a post on pinch/zoom's blog Swipe, Fling discusses the "Anatomy of a HTML5 Mobile App" and what developers will need to get started, what the pitfalls are and why HTML5 is so difficult. HTML5 is a lot like HTML, just more advanced. Fling says that "if you know HTML, then chances are you'll understand what's new in HTML5 in under an hour." Yet, he also says that HTML5 is almost nothing without Javascript and CSS. Device detection, offline data, Javascript tools, testing, debugging and themes are issues that need to be resolved with the tools at hand. One of the big challenges that developers face is the need to fully comprehend Javascript. That starts from the most basic of codes on up. Fling says that many developers cannot write Javascript without the aid of frameworks like Prototype, MooTools, jQuery or Scriptaculous. That would not be so much of a problem if all an application consisted of was functionality and theme, but the data and multiple device requirements of apps and working with the HTML5 code means that troubleshooting a Web application can be extremely difficult if a developer does not know what to look for in Javascript. Fling breaks down the three parts of the Javascript stack that is required in building HTML5 apps - hybrid, core and device scripts. Then there is CSS. Fling likens CSS to the make, model, interior and attention to detail of a car. "Javascript definitely influences our experience as well, but they are the machinations out of view," Fling wrote. "We absolutely need it to be there, but as any Top Gear fan can tell you - power under the hood doesn't always equal a powerful experience." So, HTML5 can get the job. But can it do the job? Fling says yes, but with these caveats:

Summary: Collaborative document editing means multiple editors being able to edit a shared document at the same time.. Live and concurrent means being able to see the changes another person is making, keystroke by keystroke. Currently, there are already a number of products on the market that offer collaborative document editing. Some offer live concurrent editing, such as EtherPad and SubEthaEdit, but do not offer rich text. There are others that offer rich text, such as Google Docs, but do not offer a seamless live concurrent editing experience, as merge failures can occur. Wave stands as a solution that offers both live concurrent editing and rich text document support.  The result is that Wave allows for a very engaging conversation where you can see what the other person is typing, character by character much like how you would converse in a cafe. This is very much like instant messaging except you can see what the other person is typing, live. Wave also allows for a more productive collaborative document editing experience, where people don't have to worry about stepping on each others toes and still use common word processor functionalities such as bold, italics, bullet points, and headings. Wave is more than just rich text documents. In fact, Wave's core technology allows live concurrent modifications of XML documents which can be used to represent any structured content including system data that is shared between clients and backend systems. To achieve these goals, Wave uses a concurrency control system based on Operational Transformation.

Page after page of links to experiments using advanced features of the Webkit-based Google Chrome. But update to Chrome 2.x before playing.

Flash just died. Webkit and HTML-plus are the winners.

Move over Flipboard, Push Pop and TreeSaver.  Here comes OnSwipe.  Packaging a Web site for a highly interactive and mobile world just got easier. excerpt: OnSwipe does something web developers should have been racing to accomplish ever since the iPad was first unveiled: it makes a website -- any website -- into a tablet-friendly experience. (It's already available to everyone who publishes their blog on Wordpress.com.) It uses HTML5 to make a site feel like an app, even though it's running in the browser. Onswipe points to a future of tablet media delivery that is incredibly simple, even boring: Websites that are designed to look good on tablets. Given the history of creating alternate designs for sites in order to make them mobile-friendly, why anyone ever imagined it would be otherwise is baffling. Probably, it was wishful thinking. IPad magazine app sales are tanking. Media aggregation apps like Flipboard and Zite are re-atomizing publishers' content into pleasurable, full-screen, mostly ad-free experiences. The great do-over that tablets were to represent for publishers like Condé Nast -- a chance to put the free-content genie back in the bottle, and charge for admission -- appears to have gone bust. Onswipe and the startups that will inevitably follow in its wake are the final nail in the coffin of the dream of appification of magazines and other media content

Good video demonstration of Mailbox, the new iOS app that will be released in the future for Android and the desktop.  Excellent Productivity issue discussion, as the founder of Mailbox explains what they are trying to do.  An excellent video coupled with a great interview and explanation of mobile productivity.   excerpt: "He asked himself, "What are people trying to do with email? What are the goals?" He started with Apple's Mail app for iPhone, which people were already familiar with, and injected elements of to-do apps he liked, since increasingly people are using their inboxes as to-do lists. The point was to create an experience that was distinctly mobile - an app that would let you take meaningful action while you're in line at Starbucks. Mailbox needed to intelligently display emails so you can parse and deal with them as quickly as possible. Most email apps require two or three taps to archive an email - perhaps the most common action you take on emails while you're mobile - but Mailbox only requires one: a swipe to the side. "Our biggest a-ha moment was when we realized that the primary use case of email on the phone is triage," Underwood says. Mailbox takes the reality of people using their inboxes as to-do lists and and builds on what Mail and Sparrow did right (push notifications and nicely threaded messages, respectively). SNOOZING MESSAGES To conserve space, Mailbox turns email conversations into SMS-like bubbles, which lets you quickly fly through an entire email chain. Once you've read a message, it shrinks in size so skimming threads is a snap. "Email will feel more and more like chat, and we'll continue to iterate towards that," Underwood says. "EMAIL WILL FEEL MORE AND MORE LIKE CHAT, AND WE'LL CONTINUE TO ITERATE TOWARDS THAT." Mailbox introduces a few other gestures, such as a swipe to the left that lets you "snooze" a message to be reminded about later. You can choose between a few snooze options: Later Today, This Eveni

Interesting article describing a recent press conference where Microsoft introduced their latest SkyDrive alternative to Apple's iCloud initiative.  Having had considerable experience with SkyDrive and the entire "sync-share-store" Cloud category, I left a lengthy comment. Computerworld - Microsoft is pitching its SkyDrive online storage service to Office for Mac users, calling Apple's iCloud offering "not enough" for collaboration, file sharing and anywhere-access to documents. Microsoft released an OS X SkyDrive client preview two weeks ago, adding Macs to the list of devices -- Windows, particularly the upcoming Windows 8, iOS and Windows Phone -- with native support for the Dropbox-like service. On Monday, the Redmond, Wash. developer stumped for SkyDrive on its Office for Mac website. "With the SkyDrive for Mac OS X Lion preview, SkyDrive for Windows, and the release of SkyDrive for iPad, you can save and store your important documents or other files in the SkyDrive folder in Finder and access them from anywhere," the Office for Mac team wrote on its blog.

MSOffice is now "Web ready".  The Office apps are capable of running HTML5-JavaScript apps based on a simple Web page model.  Think of this as the Office apps being fitted with a browser, and developers writing extensions to run in that browser using HTML5 and JavaScript.  Microsoft provides an Office.js library and, a developer "Web App/Page Creator"  Visual Basic toolset called "Napa" Office 365 Development Tools.  Lots of project templates. Key MSOffice apps are Word, Excel, PowerPoint and Outlook.  Develop for Office or SharePoint.  Apps can be hosted on any Web Server. excerpt: Microsoft Office 2013 Developer Environment with HTML5, XML and JavaScript.  Office.js library. "his documentation is preliminary and is subject to change. Published: July 16, 2012 Learn how to use apps for Office to extend your Office 2013 Preview applications. This new Office solution type, apps for Office, built on web technologies like HTML, CSS, JavaScript, REST, OData, and OAuth. It provides new experiences within Office applications by surfacing web technologies and cloud services right within Office documents, email messages, meeting requests, and appointments. Applies to:  Excel Web App Preview | Exchange 2013 Preview | Outlook 2013 Preview | Outlook Web App Preview | Project Professional 2013 Preview | Word 2013 Preview | Excel 2013 Preview  In this article What is an app for Office? Anatomy of an app for Office Types of apps for Office What can an app for Office do? Understanding the runtime Development basics Create your first app for Office Publishing basics Scenarios Components of an app for Office solution Software requirements"

Interesting development in the world of real time Web Apps.  Looks like Business processes and services in the Cloud are embracing HTML5, and moving fast to replace legacy client/server.  Note this is not Flash or Silverlight RiA.   excerpt: Telax Hosted Call Center, a leader in cloud contact center solutions announced the release of its HTML5-based Call Center Agent (CCA) today. Key to the development of the browser-based CCA was Websocket, a component of HTML5 that provides a bi-directional, full-duplex communication channel over a single Transmission Control Protocol (TCP) socket. Websocket is currently supported by the latest versions of Google Chrome, Apple Safari, and Firefox, making Telax's new CCA compatible with the most popular browsers in Mac environments. Before HTML5, real-time unified communication software was typically deployed as a local client because its browser-based counterparts were unable to deliver an acceptable user experience. Some browser-based clients use 3rd party software such as Adobe Flash or Sliverlight to operate adequately, but both solutions require software installation and are not mobile friendly.

"Word processors are no longer central to the computing experience, but there are still good reasons to use them. The question is, how well do the work in today's computing environment?" Interesting test of ten different word-processors, with the objective to produce an HTML Web Page. The usual suspects were tested and the results are a disaster.

Return to the bad old days Many of Apple's demos rely on "experimental" CSS3 properties to work. The exact implementation of these properties has yet to be hammered out, so browser vendors must use their best guess to determine how they should be rendered onscreen. Because of the ambiguity this introduces, it is the custom for browser vendors to attach a vendor-specific prefix to the CSS property names. Firefox uses "moz," while Safari uses "webkit," named for the browser's WebKit rendering engine. This means Web developers who want to use a specific experimental CSS feature must include the vendor-specific properties for each browser they want to support in their style sheets. It's a less than ideal situation, but the actual coding required is trivial. Apple chose not to bother for its HTML5 demo site. That would be bad enough. But Apple's demos don't work on Google's Chrome browser, either -- and Chrome also uses the "webkit" prefix for its experimental CSS3 properties (because it's also based on the WebKit rendering engine). Rather than detecting browser capabilities and degrading the user experience gracefully where features aren't supported -- as is the accepted best practice on modern browsers -- Apple chose to deliberately screen out any browser that doesn't self-identify as Safari. That's right: By forcing my browser's user agent string to identify as Safari 5, I was able to view many of the demos just fine in Firefox 3.6 on Windows. Seriously, Apple? I thought we left elaborate browser-detection scripts behind in the bad old days of the 1990s. I can't imagine anyone would want to start up the practice again, let alone one of the leading companies in the development of next-generation Web standards.

In this interview with Microsoft's Chris Capossela, he admits that OOXML is not an interoperable format - that using OOXML will result in a loss of productivity.   excerpt: "The collaboration experience end users are going to have with Office 2010 and the Web applications in the browser and Office on the phone is far superior to anything out there, whether it's from Google or anybody else. And the increase in costs to do what they're suggesting and the decrease in productivity that's going to result is something that customers will see, and then they'll choose Microsoft. The best example of that is just sharing a document. Just taking an Office document that was built in the rich client that has a piece of smart art and a watermark or a header or a footer, and then when I share that with you and you open it in the Office Web app, it looks absolutely identical to what I created. When you make edits to it and save it and I open it back up, I see exactly the edits you made and all the stuff I had in there originally. If you do that exact same thing with Google or Zoho or OpenOffice, you lose stuff. And that means loss of productivity."

Excellent Wave coverage from Scott M. Fulton III.  The Hollywood Movie industry use case scenario is very interesting.  But Scott is one of the few people to draw an analogy between Google Wave convergence of concurrent communications and collaborative content and the early days of the Microsoft Office Productivity Platform where we saw DDE, OLE and MAPI rise and rule. Excerpt: Today, Google is expected to invite as many as 100,000 more participants into the private beta of its concurrent communications system, called Wave. As that happens, many more participants will be able to not only communicate with one another in a more granular form of real-time, but potentially collaborate on work and projects. It's that latter part of the program that's supposed to congeal at some point into a collective sense of purpose. But this time, unlike Microsoft's first experiments with Dynamic Data Exchange between applications on the same computer three decades ago, there isn't yet a clear, single purpose for the system. No question it could bring individuals as close together as people separated by indefinite distance could become; but as to the question of what they do with one another once they do get together, Google is hoping this question -- like so many others it puts out there in the open -- resolves itself. Yesterday, Google offered links to a number of different independent assessments of the possible, eventual purpose of Google Wave, though it offered them as use-case scenarios rather than projections of possible goals for the product...which is what many actually were.

We can all learn a lot of lessons from the history of DDE/OLE/ OLE3/COM /ActiveX/DCOM /COM+ (you can start reading up on Wikipedia to get some background) and how we went from everyone using best-of-breed standalone apps to one integrated, nearly monolithic Office. It basically all started with copy and paste. People who never spent a lot of time in singletasking, character-mode operating environments like the DOS command line don't recall that simply copying-and-pasting information between apps was difficult at the time. And part of the revelation of Windows for mainstream users (or Mac, for leading-edge tech fans), was being able to easily share data in that way. This was different than what Unix users were used to with the command-line pipe, or from what most applications do with feeds today, in allowing structured information flows between applications. There's a desire to combine data from different sources in an arbitrary way, and to have the user interface display the appropriate tools for whatever context you're in. The dominant model here, probably because of the influence of the early PARC demos, is to have toolbars or UI widgets change depending on what kind of content you're manipulating. Microsoft was really into this in the early 90s with OLE2, where your Word toolbars would morph into Excel toolbars if you double-clicked on an embedded spreadsheet. It was ungainly and ugly and slow, especially if you had less than an exorbitant 8MB of RAM, but the idea was pretty cool. And it still is. People are so focused on data formats and feeds that they're ignoring consensus around UI interoperability. The Atom API and Metaweblog API give me a good-enough interface if I want to treat a discrete chunk of information (like a blog post) as an undifferentiated blob. But all the erstwhile spec work around microformats and structured blogging (I forget which one is for XML and which one's for XHTML) doesn't seem to have addressed user experience or editing behavior