Group items tagged

Well, not quite.  More IBM happy talk about interoperability and easy document interchange.  While i agree with the static versus interactive - collaborative document perspective, it's far more complicated. Today we have a world of "native"  docs and "visual" docs.   Native docs are bound to their authoring productivity environment, and are stubbornly NOT interchangeable.  Even for ODF and OOXML formats. Visual documents are spun from natives, and they are highly interchangeable, but interactively limited.  They lack the direct interaction of native authoring environments.  The Visual document phenomenon starts with PDF and the virtual print driver.  Any authoring application(s) in a productivity environment can print a PDF using the magic of the virtual print driver.   In 2008, when ISO stamped PDF with "accessibility tags", a new, highly interactive version of PDF was offically recognized.  We know this as "Tagged PDF".  And it has led the sweeping revolution of wide implementation of the paperless transaction process. The Visual Document phenomenon doesn't stop there.  The highly mobile WebKit revolution ushered in by the 2008 iPhone phenomenon led to wide acceptance of highly interactive and collaborative, but richly visual versions of SVG and HTML5-CSS3-JSON-JavaScript documents. Today we have SVG-HTML+ type visually immersive documents spun out of Server side publication presses such as FlipBoard, Cognito cComics, QWiki, Needle, Sports Illustrated, Push Pop Press, and TreeSaver to name but a few.   Clearly the visually immersive category of documents is exploding, but not for business - productivity documents.  Adobe has proposed a "CSS Regions" standard for richly immersive layout that might change that.  But mostly i think the problem for business documents, reports and forms is that they are "compound documents" bound to desktop productivity environments and workgroups. The great transition from desktop/workgroup productivity environme

Good article on the increasing use of HTML5 for business apps.  The focus is on mobile devices, even though HTML5 clearly targets anything capable of running a WebKit class browser.  The article also demonstrates, albeit unwittingly, the use of HTML5 as a cloud platform "Compound Document" model.  Something far more important than the comparatively limited focus of BI and CRM mobility apps.   A Cloud Producitvity Platform will replace the legacy Desktop Productivity Platform anchored on Microsoft's Windows-MSOffice workgroup networking.  Just as Compound Documents were the fuel of desktop productivity apps and services, a new breed of compound documents will fuel cloud productivity based workgroups.  The article even demonstrates the basics of embedding charts, interactive feeds, media  and database streams in HTML5 document interfaces.  Still missing real time messaging between apps, but clearly the HTML5 cloud compound document model has arrived. excerpt: HTML5 will lead to richer mobile BI and CRM apps that can be used across browsers and devices. HTML has evolved considerably since it was first mapped out by Tim Berners-Lee more than 20 years ago. Now we're up to HTML 5.0, which could have a significant effect on the business intelligence and CRM landscape.

Interesting chart describes the massive transition of small and medium sized businesses to the Cloud.  Cloud based eMail and messaging leads the way.  Top two reasons for the great transition?  Cost reduction and productivity improvement. Unfortunately this article fails to describe what this great transition to the Cloud means to legacy productivity systems - most of which are provided and provisioned by Microsoft.  What happens to desktop and workgroup based business systems when the local data and transaction processing server systems are moved to the Cloud?  How are desktop and workgroup systems re written or migrated? Another factor missing from this article is any discussion of what happens to productivity when communications, content and collaborative computing are interoperably entwined throughout the application layer?  We know that the legacy Windows productivity platform seriously lacked communications capabilities.  This fact greatly reduced expected productivity gains.   excerpt: Microsoft commissioned the study of 3,000 small and medium sized businesses in 13 countries. The survey was conducted by Wayland, Mass.-based research firm Edge Strategies. The most commonly used cloud services are email, instant messaging, voice communications, and backup. Edge also looked at SMB cloud plans over the next three years and the same cloud services also are in the IT plans of those embracing the cloud. From this data, it certainly could be argued that SMBs seem to be quick to embrace the cloud in order to enhance communication. It makes sense: in small business, communication is key to ensure rapid growth. The biggest motivators for migration to the cloud among SMBs is to save money (54 percent), followed by increases in productivity. Decision makers also mentioned flexibility as a fairly common response. Of those already using the cloud, 59 percent reported productivity increases as a result. SMB cloud adoption begins to acclerate, study finds http:/

The king of clicks returns!  No doubt there was a time when the mere mention of ODF and the now legendary XML "document" format wars with Microsoft could drive click counts into the statisphere.  Sorry to say though, those times are long gone. It's still a good story though.  Even if the fate of mankind and the future of the Internet no longer hinges on the outcome.  There is that question that continues defy answer; "Did Microsoft win or lose?"  So the mere announcement of supported formats in MSOffice XX is guaranteed to rev the clicks somewhat. Veteran ODF clickmeister SVN does make an interesting observation though: "The ironic thing is that, while this was as hotly debated am issue in the mid-2000s as are mobile patents and cloud implementation is today, this news was barely noticed. That's a mistake. Updegrove points out, "document interoperability and vendor neutrality matter more now than ever before as paper archives disappear and literally all of human knowledge is entrusted to electronic storage." He concluded, "Only if documents can be easily exchanged and reliably accessed on an ongoing basis will competition in the present be preserved, and the availability of knowledge down through the ages be assured. Without robust, universally adopted document formats, both of those goals will be impossible to attain." Updegrove's right of course. Don't believe me? Go into your office's archives and try to bring up documents your wrote in the 90s in WordPerfect or papers your staff created in the 80s with WordStar. If you don't want to lose your institutional memory, open document standards support is more important than ever. "....................................... Sorry but Updegrove is wrong.  Woefully wrong. The Web is the future.  Sure interoperability matters, but only as far as the Web and the future of Cloud Computing is concerned.  Sadly neither ODF or Open XML are Web ready.  The language of the Web is famously HTML, now HTML5+

Comment posted 1 week ago in reply to Zzgomes .....  by Ed Carp.  Finally someone who gets it! OBTW, i replaced Windows 7 with Linux Mint over a year ago and hope to never return.  The thing is though, i am not a member of a Windows productivity workgroup, nor do i need to connect to any Windows databases or servers.  Essentially i am not using any Windows business process or systems.  It's all Internet!!! 100% Web and Cloud Services systems.  And that's why i can dump Windows without a blink! While working for Sursen Corp, it was a very different story.  I had to have Windows XP and Windows 7, plus MSOffice 2003-2007, plus Internet Explorer with access to SharePoint, Skydrive/Live.com.  It's all about the business processes and systems you're part of, or must join.   And that's exactly why the Linux Desktop has failed.  Give Cloud Computing the time needed to re-engineer and re-invent those many Windows business processes, and the Linux Desktop might suceed.  The trick will be in advancing both the Linux Desktop and Application developer layers to target the same Cloud Computing services mobility targets.  ..... Windows will take of itself.   The real fight is in the great transition of business systems and processes moving from the Windows desktp/workgroup productivity model to the Cloud.  Linux Communities must fight to win the great transition. And yes, in the end this all about a massive platform shift.  The fourth wave of computing began with the Internet, and will finally close out the desktop client/server computing model as the Web evolves into the Cloud. excerpt: Most posters here have it completely wrong...the *real* reason Linux doesn't have a decent penetration into the desktop market is quite obvious if you look at the most successful desktop in history - Windows.  All this nonsense about binary driver compatibility, distro fragmentation, CORBA, and all the other red herrings that people are talking about are completely irrelevant

Google "Innovation Nation" Conference in Washington, DC had an interesting conversation thread; that the move to Cloud Computing embraces a move for individual productivity to group productivity.  Not sure i agree with that.  The Windows Desktop-WorkGroup Productivity environment has dominated business since 1992.  Maybe Google might instead focus on the limited access of desktop workgroups and the fact that productivity was horribly crippled by the the PC's lack of communication.  The Web/Cloud magically combines and integrates communication with content and computation.  This is what makes cloud collaboration a genuine leap in productivity - no matter what the discipline.  Here's a question for Google: What's the productivity difference between desktop collaboration and cloud-collaboration? excerpt:  The meeting is the staple of corporate life. The whole day revolves around when a meeting will be, who will be there and what needs to be discussed. Yet, is this rote practice may have become counter-productive in today's world of the always on, always connected workplace. Google's enterprise vision is to leverage mobility and the cloud to change the fundamental way people work. Workforce productivity used to be about how you can optimize individual output. Take all those individuals, put their output together and have a meeting to sort it all out. Google thinks that by putting all that functionality into a cloud environment, workers can use whatever device they want and always be working as a group towards on the mission. A faster, more secure, more cost efficient workplace will be the result. "The main message is that to be an effective [enterprise], we need to change from individual productivity to group productivity,"

excerpt: The trend in Office development is the migration of solutions away from in-application scripted processing toward more data-centric development. Of course this is a primary purpose of Open XML, and it is great to see the amount of activity in this area. We've seen customers scripting Word in a server environment to batch process / print documents or for other automation tasks. In reality Word isn't built to do that on a large scale, it is better to work directly against the document rather than via the application whenever possible. The Open XML SDK unlocks a "whole nuther" environment for document processing, and gets you out of the business of scripting client apps on servers to do the work of a true server application (not to mention the licensing problems created by installing Office on a server). comment:  Gray makes a very important point here.  The dominance of the desktop based MSOffice Productivity Environment was largely based the embedded logic driving "in-process" documents that was application and platform (Win32 API) specific.  Tear open any of these workgroup-workflow oriented compound documents and you find application specific scripts, macros, OLE, data bindings, security settings and other application specific settings.  These internal components are certain to break whenever these highly interactive and "live" compound documents are converted to another format, or application use.  This is how MSOffice documents and the business processes they represent become "bound" to the MSOffice Productivity Environment. What Gray is pointing to here is that Microsoft is moving the legacy Productivity Environment to an MSWeb based center where OpenXML, Silverlight, CAML, XAML and a number of other .NET-WPF technologies become the workgroup drivers.  The key applications for the MS WebStack are Exchange/SharePoint/SQL Server.  To make this move, documents had to be separated from the legacy desktop Productivity Environment settings. Note th

Finally! Someone who gets it. For an office suite to be considered as an alternative to MSOffice, it must be designed with multiple levels of compatibility. It's not just that the "feature sets" that must be comparable. The guts of the suite must be compatible at both the file format level, and the environment level. Randall put's it this way; "It's the ecosystem stupid". The reason ODF failed in Massachusetts is that neither OpenOffice nor OpenOffice ODF are designed to be compatible with legacy and existing MSOffice applications, binary formats, and, the MSOffice productivity environment. Instead, OOo and OOo-ODF are designed to be competitively comparable. As an alternative to MSOffice, OpenOffice and OpenOffice ODF cannot fit into existing MSOffice workgroups and producitivity environments. Because it s was not designed to be compatible, OOo demands that the environment be replaced, rebuilt and re-engineered. Making OOo and OOo-ODF costly and disruptive to critical day-to-day business processes. The lesson of Massachusetts is simple; compatibility matters. Conversion of workgroup/workflow documents from the MSOffice productivity environment to OpenOffice ODF will break those documents at two levels: fidelity and embedded "ecosystem" logic. Fidelity is what most end-users point to since that's the aspect of the document conversion they can see. However, it's what they can't see that is the show stopper. The hidden side of workgroup/workflow documents is embedded logic that includes scripts, macros, formulas, OLE, data bindings, security settings, application specific settings, and productivity environment settings. Breaks these aspects of the document, and you stop important business processes bound to the MSOffice productivity environment. There is no such thing as an OpenOffice productivity environment designed to be a compatible alternative to the MSOffice productivity environment. Another lesson from Massach

One of the "Lessons of Massachusetts" is that the key lock-in point for Microsoft's monopoly is their iron fisted control of the productivity environment, anchored by MSOffice and the Windows local workgroup client/server system.  Key to office productivity is the compound document model that fuels every business process and business productivity system.  It's the embedded logic and database connectivity (OLE, ODBC, MAPI and COM ActiveX controls) that juice the compound document model.   Convert a compound document to another format (or PDF), and you BREAK the both the document, AND THE BUSINESS PROCESS!!!! It was the breaking of the business process that stopped Massachusetts from moving to the Open Document Format !!!! So now comes a story with consumer sales vs enterprise sales numbers that seemingly shatter the Lessons of Massachusetts.  How is that? My take is that the numbers Microsoft touts are true.  Consumers are making new purchases - NOT enterprises.  The simple truth is that, as Microsoft introduces new OS and Application Services geared to Mobile / Cloud Computing, these new systems BREAK legacy business systems.  It's still way too costly for businesses to transition to the new models. Eventually though, businesses will replace those legacy business productivity systems with Mobile / Cloud Computing systems.  And it will be a rip-out-and-replace transition; not the gradual "value-added" transition everyone hopes Microsoft will provide.   Interesting stuff. excerpt: "If Microsoft is an enterprise company, then why is it spending so much time and money on stuff like Bing, Xbox, Windows Phone, and the Surface RT? It should be going all-in on cloud computing and services. If you were to ask Microsoft's CEO Steve Ballmer, his answer would probably be: It's a dumb question, we're both. In an interview with Jason Pontin at MIT Technology Review, he said: ""Our number-one thing is supplying products to consumers. That's kind of what we do.

Note that rip-out-and-replace to get to the cloud is a very risky strategy for MSFT because the company forfeits its vendor lock-in advantage; the question for the enterprise then becomes "replace with what?" The answer in many cases will be non-Microsoft services. And traditionally, what the enterprise uses has driven what enterprise workers use at home far more than vice versa.

Web site for Andreessen Horowitz VC. List of blogs for general partners. The reason for linking into a16z is the $11.2 Million they invested in Meteor! Meteor is awesome. My guess is that Meteor will provide a very effective Cloud platform to replace or extend the Windows Client/Server business productivity platform. Many VC watchers are wondering if a16z can recover the investment? Say what? IMHO this is for all the marbles. Platform is everything, and Cloud Computing is certain to replace Client/Server over time. Meteor just move that time frame from a future uncertainty to NOW. The Windows Productivity Platform has dominated Client/Server computing since the introduction of Windows 4 WorkGroups (v3.11) in 1992. Key technologies that followed or were included in v3.11 were DDE, OLE, MAPI, ODBC, ActiveX, and Visual Basic scripting - to name but a few. Meteor is an open source platform that hits these technologies directly with an approach that truly improves the complicated development of all Cloud based Web Apps - including the sacred Microsoft Cow herd of client/server business productivity apps. Meteor nails OLE and ODBC like nothing i've ever seen before. Very dramatic stuff. Maybe they are nailing shut the Redmond coffin in the process - making that $11.2 Mill a drop in the bucket considering the opportunity Meteor has cracked open. The iron grip Microsoft has on business productivity is so tight and so far reaching that one could easily say that Windows is the client in Client/Server. But it took years to build that empire. With this investment, Meteor could do it in months. Compound documents are the fuel in Windows business productivity and office automation systems. Tear apart a compound document, and you'll find embedded logic for OLE and ODBC. Sure, it's brittle, costly to develop, costly to maintain, and a bear to distribute. Tear apart a Meteor productivity service and you'll find the same kind of OLE-ODBC-Script

Is Intel right?  Is there a "compatibility-interoperability" problem between Windows RT Office (ARM) and legacy (x86) Windows MS Office productivity environments?  It seems to me that the entire reason iPAD, Android and other ARM based tablet systems want MSOffice and MSOffice Visual Document Viewers is exactly because they want and expect a high level of compat-interop with legacy Windows productivity workgroups and client/server systems. What's the truth?  And is there anything x86 providers like Intel and AMD can do about compat-interop and the unstoppable cloud-mobility revolution? excerpt: The Asus tablet has a quad-core Tegra 3 processor from Nvidia. Windows RT comes preloaded with Office 15, a group of widely used productivity applications. Microsoft has said it had to re-engineer Windows RT to deal with expectations for ARM based devices, which include all-day connectivity and low power consumption. The tablet also has an 8-megapixel camera at the rear with LED flash, and a 2-megapixel camera at the front. It has 2GB of RAM, 32GB of storage, Wi-Fi and Bluetooth 4.0. Intel has already started the war of words against ARM around Windows 8, with Intel's CEO Paul Otellini saying that ARM devices will be incompatible with existing Windows applications and drivers. But analysts have said that Windows RT devices will likely be attractive to users who have few ties with legacy Windows PCs. Low prices could also attract users to Windows on ARM devices.

The free CloudON app for iPAD provides a very nice ribbon interface for viewing and editing MSOffice XML documents.  Supports important workgroup features like "change tracking", show or hide markup, make and view comments, restrict editing, and compare and combine versions.  Very cool. Lacks support for custom add-ons, templates, auto-correct settings, and other advanced features may limit the program's usefulness.  Time to do some testing.  Hope Florian catches this post :) excerpt: Support for Office XML file types, and a ribbon to boot ...... Speculation continues as to whether -- most say when -- Microsoft will release a version of Office for the iPad. (CNET blogger Zack Whittaker cites sources predicting a November arrival.) It's not like you have to wait months to create and edit Word, Excel, and PowerPoint files on your iPad. Last June I described how to use Google Docs and Google Cloud Connect to edit Word and Excel files on an iPad for free. The end of that story noted the likely arrival of iPad apps supporting Office file formats. One of the most popular of these is the $15 Quickoffice, a program that was recently acquired by Google. But before you shell out for an Office alternative, check out the free CloudOn app, which now connects to Google Drive and Box accounts as well as Dropbox accounts. Other new features in the latest release let you send files as e-mail attachments and open PDFs. (See Lance Whitney's post on the Internet & Media blog for more on the program's PDF features.) CloudOn's ribbon is a big departure from the Quickoffice interface, which look nothing like Office. (Of course, many people will prefer the clean, clutter-free look of Quickoffice.) None of the Office extras, but all the essentials: In a group setting CloudOn's lack of support for custom add-ons, templates, auto-correct settings, and other advanced features may limit the program's usefulness. Still, the word processor lets you track and accept changes, show or

Byron Deeter is right, but perhaps he's holding back on his reasoning.  Silicon Valley is all about platform, and platform plays only come about once every ten to twenty years.  They come like great waves of change, not replacing the previous waves as much as taking away and running with the future.   Cloud Computing is the fourth great wave.  It will replace the PC and Network Computing waves as the future.  It is the target of all developers and entrepreneurs.   The four great waves are mainframe, workstation, pc and networked pc, and the Internet.  Cloud Computing takes the Internet to such a high level of functionality that it will now replace the pc-netwroking wave.  It's going to be enormous.  Especially as enterprises move their business productivity and data / content apps from the desktop/workgroup to the Cloud.  Enormous. The key was the perfect storm of 2008, where mobility (iPhone) converged with the standardization of tagged PDF, which converged with the Cloud Computing application and data model, which all happened at the time of the great financial collapse.   The financial collapase of 2008 caused a tectonic shift in productivity.  Survival meant doing more with less.  Particularly less labor since cost of labor was and continues to be a great uncertainty.  But that's also the definition of productivity and automation.  To survive, companies were compelled to reduce labor and invest in software/hardware systems based productivity.  The great leap to a new platform had it's fuel; survival. Social applications and services are just the simplest manifestation of productivity through managed connectivity in the Cloud.  Wait until this new breed of productivity reaches business apps!  The platform wars have begun, and it's for all the marbles. One last thought.  The Internet was always going to win as the next computing platform wave.  It's the first time communications have been combined and integrated into content, and vast dat

wow.  Six years and all they have migrated are 2,500 out of 14,0000 desktops!  The curse of the Microsoft Productivity Environment strikes again as legacy workgroups, workflows and the mesh of compound documents that drive them prove to be very stubborn.  The funny thing is that, as Munich struggles with this 1995 level desktop transition, Microsoft is preparing to move those very same legacy productivity environments to a proprietary Web Productivity Platform.  I wonder what Munich's Web plans are? excerpt: Schießl says the transition required enormous background effort which involved eliminating many IT dependencies created by individual vendors over the years. More than 20,000 templates had to be consolidated and converted into new templates, macros or web applications. Most templates and text blocks are now managed via the WollMux program, which was released in 2008. Schießl said that the developers also had to adapt a number of corporate applications such as SAP for use with ODF. According to the review, another achievement in 2009 was the establishment of Linux client pilot areas as a step towards the final aim of migrating all twelve of the city administration's departments to Linux. Schießl says this was the last fundamental step required to enable general client migration in the coming years. Although only 2,500 of around 14,000 workstations have been converted to the custom-built basic LiMux client, the hardest part was to get them all up and running, which required going over inconsistent IT infrastructures that had developed over the years and training the IT staff for the technical switch. As Robert Pogson observes in his blog, six and a half years after the decision was made to switch to free software, the Munich Linux pioneers have completed about 80 per cent of the project's total workload.

JUDGMENT OF THE COURT OF FIRST INSTANCE (Grand Chamber) 17 September 2007 (*) (Competition - Abuse of dominant position - Client PC operating systems - Work group server operating systems - Streaming media players - Decision finding infringements of Article 82 EC - Refusal of the dominant undertaking to supply and authorise the use of interoperability information - Supply by the dominant undertaking of its client PC operating system conditional on the simultaneous acquisition of its media player - Remedies - Appointment of an independent monitoring trustee - Fine - Determination of the amount - Proportionality) In Case T-201/04, Microsoft Corp., established in Redmond, Washington (United States), represented by J.-F. Bellis, lawyer, and I. Forrester QC,

Microsoft's free "Office Starter" suite will be able to fully open and display complex OOXML - 2010 MSOffice documents.  But they will not be able to execute macros or edit embedded logic such as Scripts, Macros, OLE, and ODBC connectors.  That's a killer for workgroup-workflow oriented business documents.  A category of "compound documents that includes forms, reports, compound documents and workflow logic. As for what users can do with the applications, Capossela said that Word will be capable of opening and displaying even the most complex documents. However, Office Starter users won't be able to use macros, create automated tables of contents, or add comments, though they will see comments added by others. The approach with Excel is similar, with users able to view and edit documents, but not create their own pivot tables and pivot charts, for example.

Good stuff!  Be sure to watch the YouTube video.  There is a demo of how a Google Docs and MSWord collaborative document gets synchronized.  Notice the layout mismatch.  They do however seem to understand the problems of the advanced formatting common to compound documents and "in-process" workgroup documents. excerpt:  OffiSync is launching an all-new version of its Microsoft Office to Google Docs synchronization tool, a plugin that's a "must-have" for anyone still straddling the two worlds of office suites: that is, the desktop-based world of Microsoft software and the web-based world of Google Docs. In the updated version of OffiSync, set to arrive minutes from now, you'll be able to co-author documents in real-time between Microsoft Office and Google Docs, no matter what version of the Office software you use. There are a few other new features too, including improvements to search, added Google Sites support and the ability to store any file type, but it's the co-authoring feature that's today's biggest reveal.

Soonr is an extremely well done document management service alternative to DropBox, Box.net, SyncDocs and a host of other services in this new Cloud sector of integrated document services.  What makes Soonr different is there focus on project management, with resource management for documents, collaborative notes and workgroups.  Nicely done.  Great iPAD interface.  Needs wikiWORD in the worst way.  Especially in the wake of Jive's purchase of OfficeSync. excerpt: Soonr is the first cloud file storage service to offer integrated editing for Microsoft Office documents on the iPad. Unlike cobbling together of file storage apps such as Dropbox and SugarSync with editing apps such as QuickOffice and Documents-To-Go, Soonr brings it all together so you can directly edit any files stored in the cloud using a single app. No configuration, no hassle, no cross-app interdependency. It also works offline when you don't have a Wi-Fi connection and will sync back up when you do. And you can store, share, access, search, edit and sync your files from any tablet securely through Soonr.

Lengthy discussion about Cloud computing innovation and interoperability.  Lots of quotes.  Looks like the consulting space for cloud computing is exploding.  No mention though of the great transition from Desktop/WorkGroup Productivity to Cloud/Web Productivity Platforms.  Obviously we need more experts :) excerpt: As the hype over cloud computing evolves into a more substantive discussion, one thing has become clear -- customers do not want to be locked into a single cloud provider. They would like the freedom to move among the clouds -- ideally from public to private and back again. This would give customers the freedom to switch providers as their computing needs grow or shrink, and the ability to move applications and workloads around as their business requirements change.

Wow!  This reads like a premature press release, but if true it's breakthru technology.  I wonder though why Ericom is targeting education?  Seems this innovation would be of immediate importance to enterprise and SMB businesses struggling with the great transition from desktop/workgroup productivity systems to Web Productivity Platforms. excerpt: Ericom has released AccessNow, a pure HTML5 remote desktop (RDP) client that runs within a Web browser without the need to install anything on the client device. AccessNow provides accelerated remote access to applications and desktops running on Windows Terminal Services, remote desktop services (RDS), and virtual desktop infrastructure (VDI), including applications, remote desktops, VMware View desktops, virtual desktops running on Microsoft Hyper-V, and other hypervisors. AccessNow works on any device with an HTML5-capable browser, such as Chrome, Safari, Firefox, Opera, and others, without the use of browser plugins, Java, Flash, ActiveX, Silverlight, or other underlying technology. Internet Explorer is also supported, although it does require the Chrome Frame plugin. AccessNow uses only the standard Web technologies: HTML, CSS, and JavaScript. This approach helps IT administrators maintain centralized control of school resources. It also enables students and staff to use any Internet-enabled device, including smartphones, tablets, and Chromebooks, to do their work anywhere and anytime.