The document discusses the evolution of using the web as a real application platform. It outlines key technologies like HTML5, JavaScript, and WebGL that have advanced the capabilities of web applications. The document also notes shortcomings in earlier versions of the web around user interaction, performance, and compatibility issues. However, new technologies and browser improvements have helped address many of these issues. The document concludes that the web is becoming a viable platform for developing full-featured applications that combine the benefits of installed software and web-based applications.
The document discusses the WebKit project and how to contribute to it. It describes WebKit as an open source web browser engine used in browsers and other applications. It provides information on WebKit's architecture, goals, features, ports to different platforms, and the WebKit2 API. It also discusses the large WebKit community, how work is tracked, and how developers can contribute through bug fixing, new features, or creating new ports.
This document discusses options for integrating applications with IBM Connections, both in the cloud and on-premises. It demonstrates techniques used by the ProjExec application to authenticate users single sign-on and use OAuth tokens to access Connections APIs. The document also covers customizing the user interface by adding items to the navigation bar and using different widget technologies. It recommends developing applications to work across platforms by loading content in an iframe and supporting multiple integration options.
AJAX and Silverlight are web application development technologies. AJAX uses a combination of technologies like HTML, CSS, DOM, XML, XSLT, JavaScript, and XMLHttpRequest to make asynchronous requests in the background without interfering with the existing page. Silverlight is a Microsoft plugin that allows developers to use .NET languages to create rich multimedia applications for the web. While AJAX relies mainly on JavaScript and XMLHttpRequest, Silverlight relies on the .NET framework. AJAX supports cross-platform development while Silverlight only supports Windows, Linux with Moonlight, and Mac OS.
This document discusses building a core application that can be deployed on different servers using a Java core. It provides examples using the Vaadin framework to build a basic application, deploying it on Apache Tomcat and IBM WebSphere Application Server. It also discusses setting up the application on IBM Domino using an OSGi plugin project. Additional topics covered include handling multiple authentication methods and implementing a data abstraction layer to make the application agnostic to the backend data store. The goal is to allow writing applications once and deploying them on any server with minimal changes.
This document discusses different programming environments for developing BlackBerry applications, including QNX, Adobe AIR, Android, and WebWorks. It provides details on each environment, such as supported APIs, tools, and frameworks. It also discusses packaging and deploying applications created with these environments.
This document discusses the technologies behind the HP webOS platform, including Enyo and Node.js. It provides an overview of Enyo, describing it as a framework for building web applications that targets developers and supports flexible layouts, device and desktop applications, and code reuse through components. It also discusses Node.js and how it is used as the runtime for webOS services, allowing applications to access system services and process data without blocking the user interface. The architecture of webOS applications is also summarized, including how the Enyo framework is used to build the user interface and application structure.
The document discusses several key technologies for developing Java web applications, including Java Servlet technology, WebWork framework, Spring framework, and Apache Maven build tool. It provides an overview of how each technology addresses common problems like stateless communication, business logic implementation, view generation, and data access overhead. Examples are given showing how WebWork and Spring can be used together with Maven to build a simple "Hello World" application that follows the MVC pattern and leverages dependency injection.
The document provides instructions for setting up and configuring a project in WebWorks for Word. It outlines how to launch a project, map source document styles and the table of contents, define media type and cross-reference settings, and choose to convert the project immediately or later. The goal is to prepare the source document for conversion into optimized output files.
The story of all the pitfalls we had while transferring FTBpro.com from the good old web to a Backbone single page application... and all the great solutions we've came up with
Ponencia de Jorge del Casar en DroidconMAD2013.
Sinopsis: Cordova es un framework de desarrollo móvil de código abierto que permite usar tecnologías web standard como HTML5, CSS3 y Javascript para el desarrollo multiplataforma, evitando desarrollar en el lenguaje nativo de cada plataforma. La nueva Command Line Interface (CLI) desarrollada en Node.js te permite automatizar la creación de proyectos, adición de plataformas y plugins así como la construir la app y probarla en simuladores y dispositivos reales.
Deview 2013 mobile browser internals and trends_20131022
The document discusses browser internals and trends related to mobile browsers. It provides an overview of the major rendering engines including WebKit, Blink, and Chromium. It then focuses on specifics of Android's WebView and how it has transitioned to using the Chromium engine. Finally, it describes the multi-process architecture of Chromium which separates rendering and browser components across multiple processes for improved stability.
Sascha Corti
With Internet Explorer 9, Microsoft has entered the league of HTML 5 browsers and with its active participation in the W3C working groups, the company proves its engagements towards the new and emerging standards. Developers however are often left wondering where the boundaries are drawn between HTML5 web site, plug-in based rich internet application and smart client or “app”.
This session intends to answer this question and uses many examples to show you some of the most important enhancements introduced by HTML5, CSS3, SVG, DOM, WOFF and ECMA script. You will learn now the standards are still evolving and how Microsoft is contributing.
http://soft-shake.ch/2011/conference/sessions/microsoft/2011/09/06/introduction-to-html5.html
This document discusses optimizing jQuery and front-end performance. It covers minimizing HTTP requests, file size, and blocking behavior to improve dependency loading. It discusses optimizing initial page rendering through proper asset ordering, lazy loading, and reducing flash of unstyled content. It also discusses minimizing reflows and repaints as well as JavaScript optimizations to improve post-load responsiveness. The document provides an overview of jQuery internals and techniques for optimizing jQuery code.
The document provides an overview of various web application presentation layer solutions, including:
- HTML/XHTML - Provides basic document structure and presentation. Interactions require full page reloads. Wide reach but limited interactivity.
- DHTML - Combines HTML, JavaScript, and CSS to enable some interactivity like animations without reloading. Inconsistent cross-browser support.
- DHTML with Remote Scripting via iFrame - Uses hidden iFrames to retrieve information from the server asynchronously without refreshing the full page. Reduces server loads compared to full page reloads.
The document evaluates each solution based on criteria like user experience, processing requirements, deployment, components/customization options, backend
The Status Of Web Interoperability And Activities In China, Japan And Korea
The document discusses web interoperability activities in China, Japan, and Korea. It notes discrepancies between major browsers and efforts to address them, including guidelines on differences and solutions. It provides updates on the status of browsers and support for open standards in each country's websites and communities. Activities include compatibility testing, tools to identify issues, and governments supporting open standards adoption.
The document discusses the history and architecture of Android's WebView. It describes how WebView has transitioned from using a custom WebKit implementation to being based on the Chromium rendering engine. It also summarizes the threading models of Chrome and WebView and explains how rendering occurs in two phases of painting and compositing layers.
This document provides an agenda and overview for an introduction to ASP.NET MVC 3. It begins by discussing the motivation for MVC as an alternative to traditional ASP.NET Web Forms due to limitations like heavy view state, a complex page lifecycle, lack of separation of concerns, limited control over HTML, and low testability in Web Forms. It then covers key benefits of MVC like tight control over HTML and HTTP, a powerful routing system, testability, and being built on the ASP.NET platform. The document reviews what's new in MVC 3 like the Razor view engine and improved JavaScript support. It provides steps for creating a basic MVC application and controller. Finally, it outlines designing a
This document provides an introduction to programming terminology, concepts, and technologies for non-technical people. It outlines a training on software development lifecycles, engagement models, business domains, major programming languages, frameworks, and technologies. Key terms from front-end and back-end development, databases, DevOps, data science, and mobile apps are defined. Popular languages, frameworks, and platforms are compared, along with ratings of language popularity. Quality control techniques are briefly introduced.
I. ASP.NET is a web development platform from Microsoft used to build web applications. It provides advantages over classic ASP like separation of presentation and code for easier maintenance.
II. The ASP.NET architecture includes layers for the browser, web server, application server, business logic, and database. It uses HTTP for communication and HTML/XHTML pages.
III. Key challenges in designing web application interfaces include the stateless nature of the web, ensuring responsive and intuitive user interfaces, achieving scalability and performance, and addressing security issues.
Web technologies such as HTML5, Javascript and CSS3 are emerging as an alternative for mobile application development platform, at the same time allow the user to provide great experiences, and are simple to administer and maintain by IT organizations.
This session will discuss the status of these technologies and their feasibility for the development of mobile applications. We will also address some recommendations and considerations that must be taken to choose a strategy for developing apps based on web technologies.
The document provides an introduction to building applications using BlackBerry WebWorks. It discusses HTML5, the differences between web apps and native apps, and why developers may want to use BlackBerry WebWorks. The document then covers setting up the development environment, creating a basic "Hello World" app with HTML files and a configuration file, organizing files into folders, and using the Ripple emulator to package and test the app.
The document discusses the WebKit project and how to contribute to it. It describes WebKit as an open source web browser engine used in browsers and other applications. It provides information on WebKit's architecture, goals, features, ports to different platforms, and the WebKit2 API. It also discusses the large WebKit community, how work is tracked, and how developers can contribute through bug fixing, new features, or creating new ports.
This document discusses options for integrating applications with IBM Connections, both in the cloud and on-premises. It demonstrates techniques used by the ProjExec application to authenticate users single sign-on and use OAuth tokens to access Connections APIs. The document also covers customizing the user interface by adding items to the navigation bar and using different widget technologies. It recommends developing applications to work across platforms by loading content in an iframe and supporting multiple integration options.
AJAX and Silverlight are web application development technologies. AJAX uses a combination of technologies like HTML, CSS, DOM, XML, XSLT, JavaScript, and XMLHttpRequest to make asynchronous requests in the background without interfering with the existing page. Silverlight is a Microsoft plugin that allows developers to use .NET languages to create rich multimedia applications for the web. While AJAX relies mainly on JavaScript and XMLHttpRequest, Silverlight relies on the .NET framework. AJAX supports cross-platform development while Silverlight only supports Windows, Linux with Moonlight, and Mac OS.
This document discusses building a core application that can be deployed on different servers using a Java core. It provides examples using the Vaadin framework to build a basic application, deploying it on Apache Tomcat and IBM WebSphere Application Server. It also discusses setting up the application on IBM Domino using an OSGi plugin project. Additional topics covered include handling multiple authentication methods and implementing a data abstraction layer to make the application agnostic to the backend data store. The goal is to allow writing applications once and deploying them on any server with minimal changes.
This document discusses different programming environments for developing BlackBerry applications, including QNX, Adobe AIR, Android, and WebWorks. It provides details on each environment, such as supported APIs, tools, and frameworks. It also discusses packaging and deploying applications created with these environments.
JavaScript on HP webOS: Enyo and Node.jsBen Combee
This document discusses the technologies behind the HP webOS platform, including Enyo and Node.js. It provides an overview of Enyo, describing it as a framework for building web applications that targets developers and supports flexible layouts, device and desktop applications, and code reuse through components. It also discusses Node.js and how it is used as the runtime for webOS services, allowing applications to access system services and process data without blocking the user interface. The architecture of webOS applications is also summarized, including how the Enyo framework is used to build the user interface and application structure.
The document discusses several key technologies for developing Java web applications, including Java Servlet technology, WebWork framework, Spring framework, and Apache Maven build tool. It provides an overview of how each technology addresses common problems like stateless communication, business logic implementation, view generation, and data access overhead. Examples are given showing how WebWork and Spring can be used together with Maven to build a simple "Hello World" application that follows the MVC pattern and leverages dependency injection.
The document provides instructions for setting up and configuring a project in WebWorks for Word. It outlines how to launch a project, map source document styles and the table of contents, define media type and cross-reference settings, and choose to convert the project immediately or later. The goal is to prepare the source document for conversion into optimized output files.
The Dark Side of Single Page ApplicationsDor Kalev
The story of all the pitfalls we had while transferring FTBpro.com from the good old web to a Backbone single page application... and all the great solutions we've came up with
Ponencia de Jorge del Casar en DroidconMAD2013.
Sinopsis: Cordova es un framework de desarrollo móvil de código abierto que permite usar tecnologías web standard como HTML5, CSS3 y Javascript para el desarrollo multiplataforma, evitando desarrollar en el lenguaje nativo de cada plataforma. La nueva Command Line Interface (CLI) desarrollada en Node.js te permite automatizar la creación de proyectos, adición de plataformas y plugins así como la construir la app y probarla en simuladores y dispositivos reales.
Deview 2013 mobile browser internals and trends_20131022NAVER D2
The document discusses browser internals and trends related to mobile browsers. It provides an overview of the major rendering engines including WebKit, Blink, and Chromium. It then focuses on specifics of Android's WebView and how it has transitioned to using the Chromium engine. Finally, it describes the multi-process architecture of Chromium which separates rendering and browser components across multiple processes for improved stability.
Sascha Corti
With Internet Explorer 9, Microsoft has entered the league of HTML 5 browsers and with its active participation in the W3C working groups, the company proves its engagements towards the new and emerging standards. Developers however are often left wondering where the boundaries are drawn between HTML5 web site, plug-in based rich internet application and smart client or “app”.
This session intends to answer this question and uses many examples to show you some of the most important enhancements introduced by HTML5, CSS3, SVG, DOM, WOFF and ECMA script. You will learn now the standards are still evolving and how Microsoft is contributing.
http://soft-shake.ch/2011/conference/sessions/microsoft/2011/09/06/introduction-to-html5.html
This document discusses optimizing jQuery and front-end performance. It covers minimizing HTTP requests, file size, and blocking behavior to improve dependency loading. It discusses optimizing initial page rendering through proper asset ordering, lazy loading, and reducing flash of unstyled content. It also discusses minimizing reflows and repaints as well as JavaScript optimizations to improve post-load responsiveness. The document provides an overview of jQuery internals and techniques for optimizing jQuery code.
The document provides an overview of various web application presentation layer solutions, including:
- HTML/XHTML - Provides basic document structure and presentation. Interactions require full page reloads. Wide reach but limited interactivity.
- DHTML - Combines HTML, JavaScript, and CSS to enable some interactivity like animations without reloading. Inconsistent cross-browser support.
- DHTML with Remote Scripting via iFrame - Uses hidden iFrames to retrieve information from the server asynchronously without refreshing the full page. Reduces server loads compared to full page reloads.
The document evaluates each solution based on criteria like user experience, processing requirements, deployment, components/customization options, backend
The Status Of Web Interoperability And Activities In China, Japan And KoreaChanny Yun
The document discusses web interoperability activities in China, Japan, and Korea. It notes discrepancies between major browsers and efforts to address them, including guidelines on differences and solutions. It provides updates on the status of browsers and support for open standards in each country's websites and communities. Activities include compatibility testing, tools to identify issues, and governments supporting open standards adoption.
The document discusses the history and architecture of Android's WebView. It describes how WebView has transitioned from using a custom WebKit implementation to being based on the Chromium rendering engine. It also summarizes the threading models of Chrome and WebView and explains how rendering occurs in two phases of painting and compositing layers.
This document provides an agenda and overview for an introduction to ASP.NET MVC 3. It begins by discussing the motivation for MVC as an alternative to traditional ASP.NET Web Forms due to limitations like heavy view state, a complex page lifecycle, lack of separation of concerns, limited control over HTML, and low testability in Web Forms. It then covers key benefits of MVC like tight control over HTML and HTTP, a powerful routing system, testability, and being built on the ASP.NET platform. The document reviews what's new in MVC 3 like the Razor view engine and improved JavaScript support. It provides steps for creating a basic MVC application and controller. Finally, it outlines designing a
Meetup. Technologies Intro for Non-Tech PeopleIT Arena
This document provides an introduction to programming terminology, concepts, and technologies for non-technical people. It outlines a training on software development lifecycles, engagement models, business domains, major programming languages, frameworks, and technologies. Key terms from front-end and back-end development, databases, DevOps, data science, and mobile apps are defined. Popular languages, frameworks, and platforms are compared, along with ratings of language popularity. Quality control techniques are briefly introduced.
I. ASP.NET is a web development platform from Microsoft used to build web applications. It provides advantages over classic ASP like separation of presentation and code for easier maintenance.
II. The ASP.NET architecture includes layers for the browser, web server, application server, business logic, and database. It uses HTTP for communication and HTML/XHTML pages.
III. Key challenges in designing web application interfaces include the stateless nature of the web, ensuring responsive and intuitive user interfaces, achieving scalability and performance, and addressing security issues.
The document discusses trends in application development for mobile and cross-platform use. It notes the rise of consumerization of technology and the need to build apps that can be used on any device. This has led to changes like using HTML and JavaScript instead of platform-specific languages to allow cross-platform support. Frameworks like Backbone.js and libraries like Underscore.js can help manage the complexity of building such apps. The document also discusses considerations for responsive design, client-side architecture including MV* frameworks, and tools to support development.
HTML5 is becoming the preferred technology for automotive HMI systems due to its rich set of features that allow for the creation of robust applications. Key features include local storage options like Web Storage and IndexedDB for offline use, multimedia support through <audio> and <video> tags, device access APIs, and rendering controls like <canvas> that enable precise graphics. The emergence of HTML5 has also influenced development practices, with more use of patterns like MVC to separate application logic from presentation.
VizEx View HTML5 technology enables the display of CGM graphics in a web browser, without the requirement for a plug-in. Our popular event returns with an introduction to the technology, and the latest news on how we’re improving the technology. The event will be suitable for individuals and organizations who are new to the technology, and current customers. The developers will be on hand to answer technical questions, and explain how the technology is improving under the hood. We hope you can join us for this informative event.
In this Presentation all type of JS frameworks are discussed and by viewing this you can compare that which is the best JS framework in present time for different different purposes.
ASP.NET is a set of Web development tools offered by Microsoft. Programs like Visual Studio .NET and Visual Web Developer allow Web developers to create dynamic websites using a visual interface. Of course, programmers can write their own code and scripts and incorporate it into ASP.NET websites as well. Though it often seen as a successor to Microsoft's ASPprogramming technology, ASP.NET also supports Visual Basic.NET, JScript .NET and open-source languages like Python and Perl.
ASP.NET is built on the .NET framework, which provides an application program interface (API) for software programmers. The .NET development tools can be used to create applications for both the Windows operating system and the Web. Programs like Visual Studio .NET provide a visual interface for developers to create their applications, which makes .NET a reasonable choice for designing Web-based interfaces as well.
- SignalR provides a simple way to add real-time web functionality to applications. It allows for persistent connections and messaging between servers and clients.
- It abstracts away the various techniques for real-time communication like websockets, long polling, and server-sent events and chooses the best transport.
- SignalR uses hubs to facilitate two-way communication between clients and servers through methods. This allows for different message types and structures to be sent.
The document discusses how web applications have evolved from tightly coupled server-side models to loosely coupled JavaScript frameworks that run entirely in the browser. Key developments include rich JavaScript frameworks, HTML5 and CSS3 standards, and the proliferation of mobile browsers. This has allowed web applications to achieve a rich user experience without plugins and has freed web apps from their tightly coupled relationship to servers. Decision makers need to understand how this new architecture impacts development teams and technologies.
A general overview of HTML5, CSS 3, CSS Meedia Queries, mobile, DAP.
You might find the organically-grown hand-selected list-of-links-o-rama™ at http://my.opera.com/ODIN/blog/over-the-air-2010-bruce-lawsons-web-developments-2-0-talk to be useful.
JavaScript is a lightweight, interpreted programming language best known for enabling dynamic web page content. It was originally created in 1995 as a way to add interactivity to web pages. While primarily used for client-side scripting in web browsers, JavaScript is now also used for server-side applications through Node.js. JavaScript has evolved significantly since its creation and continues to be actively developed and improved through new specifications and implementations by browser vendors. It has become ubiquitous across web browsers and other environments due to its versatility and continued enhancements.
Open Mic to discuss the new features related to Portal and Web Content Management introduced in version 8.5. We will be covering changes related to themes,
mobile, social integration and WCM changes related to syndication and rich media aspects of the new release.
The document provides an overview of the key components that go into making a PHP and MySQL based web application. It discusses the use of HTML, CSS, JavaScript, jQuery, client-side and server-side scripting, AJAX, PHP, MySQL, code editors, tools for wireframing, image editing and more. It also covers aspects like hosting, version management, software deployment, traditional and agile development methodologies, and software documentation.
Web development concepts using microsoft technologiesHosam Kamel
This document summarizes a presentation about web development concepts using Microsoft technologies. It introduces ASP.NET as a framework for building web applications in C# or VB.NET using Visual Studio. It describes ASP.NET features like controls, page lifecycle, and different coding styles. It also discusses recent additions like AJAX, jQuery, LINQ, MVC, and the Microsoft web platform. The presentation aims to provide an overview of Microsoft web technologies and how they can help developers build web applications.
Web Application Technologies,What is servlet?
Jobs of servlet
Advantages over CGI
Why pages are build dynamically?
Servlet container
Installation & configuration
- Type 1: Integration of Tomcat server and eclipse
- Type 2: Java Servlet
Servlet Sample Example
Servlet Overview And Architecture
- Servlet Life cycle/Single Thread Model
- Interface Servlet
- HttpServlet Class
- HttpServletRequest, HttpServletResponse
Handling client request :Http request
Generating Server Response : Http status code
Handling Session
- Cookies
- Session Tracking
- URL-re writing
- Hidden Form fields
Developing Revolutionary Web Applications using Comet and Ajax PushDoris Chen
Join the asynchronous web revolution! Because Ajax-based applications are almost becoming the de facto technology for designing web-based applications, it is more and more important that such applications react on the fly, or in real time, to both client and server events. AJAX can be used to allow the browser to request information from the web server, but does not allow a server to push updates to a browser. Comet solves this problem. Comet is a technology that enables web clients and web servers to communicate asynchronously, allowing real-time operations and functions previously unheard of with traditional web applications to approach the capabilities of desktop applications. This session will start to provide an brief introduction to the asynchronous web, AJAX polling, long polling, and Streaming, explaining the Bayeux protocol, Cometd, Grizzly Comet implementation on GlassFish. Different approaches and best practices to develop comet application will also be discussed. You will learn how to develop the chat application, how to implement distance learning slideshow application, how to manage a chat application from the server and how to develop a two-player distributed game application. Attendees will take away the tactics they need in order to add multiuser collaboration, notification and other Comet features to their application, whether they develop with Dojo, jQuery, jMaki, or Prototype and whether they deploy on Jetty, Tomcat, or the GlassFish Application Server.
1) The document discusses ASP.NET 5, a new approach to building .NET on the server that features a flexible and cross-platform runtime, modular HTTP request pipeline, and cloud-optimized design.
2) It introduces ASP.NET 5 and MVC 6, which merges MVC, Web API, and Web Pages frameworks into a single framework for building web UIs and APIs.
3) A demo is presented showing the creation of an empty ASP.NET 5 application.
A brief introduction on HTML5 and responsive layoutsTim Wray
The document discusses the choice between building apps with HTML5 versus native apps. It provides an overview of new features in HTML5, including semantic layout tags, custom data attributes, new UI elements, smarter forms, CSS3, canvas graphics, audio/video support, drag and drop, offline storage, geolocation, and responsive web design. HTML5 allows building responsive mobile web experiences through features like media queries and viewport meta tags.
Similar to Transforming the web into a real application platform (20)
Book dating , international dating phgrathomaskurtha9
International dating programhttps: please register here and start to meet new people todayhttps://www.digistore24.com/redir/384521/godtim/.
get started. https://www.digistore24.com/redir/384521/godtim/
Have you ever built a sandcastle at the beach, only to see it crumble when the tide comes in? In the digital world, our information is like that sandcastle, constantly under threat from waves of cyberattacks. A cybersecurity course is like learning to build a fortress for your information!
This course will teach you how to protect yourself from sneaky online characters who might try to steal your passwords, photos, or even mess with your computer. You'll learn about things like:
* **Spotting online traps:** Phishing emails that look real but could steal your info, and websites that might be hiding malware (like tiny digital monsters).
* **Building strong defenses:** Creating powerful passwords and keeping your software up-to-date, like putting a big, strong lock on your digital door.
* **Fighting back (safely):** Learning how to identify and avoid threats, and what to do if something does go wrong.
By the end of this course, you'll be a cybersecurity champion, ready to defend your digital world and keep your information safe and sound!
seo proposal | Kiyado Innovations LLP pdfdiyakiyado
Crafting a compelling SEO proposal? Learn how to structure a winning SEO proposal template with essential elements and tips for client engagement. Elevate your SEO strategy with expert insights and examples
The advent of social media has revolutionized communication, transforming the way people connect, share, and interact globally. At the forefront of this digital revolution are visionary entrepreneurs who recognized the potential of the internet to foster social connections and create communities. This essay explores the founders of some of the most influential social media platforms, their journeys, and the lasting impact they have made on society.
Mark Zuckerberg, along with his college roommates Eduardo Saverin, Andrew McCollum, Dustin Moskovitz, and Chris Hughes, founded Facebook in 2004. Initially created as a social networking site for Harvard University students, Facebook rapidly expanded to other universities and eventually to the general public. Zuckerberg's vision was to create an online directory that connected people through their real-life social networks.
Twitter, founded in 2006 by Jack Dorsey, Biz Stone, and Evan Williams, brought a new dimension to social media with its microblogging platform. Dorsey envisioned a service that allowed users to share short, real-time updates, limited to 140 characters (now 280). This concise format encouraged rapid sharing of information and fostered a culture of brevity and immediacy.
Kevin Systrom and Mike Krieger co-founded Instagram in 2010, focusing on photo and video sharing. Systrom, who studied photography, wanted to create an app that made mobile photos look professional. The app's unique filters and easy-to-use interface quickly gained popularity, amassing over a million users within two months of its launch.
Instagram's emphasis on visual content has had a significant cultural impact. It has popularized the concept of influencers, giving rise to a new industry where individuals can monetize their popularity and reach. The platform has also revolutionized digital marketing, enabling brands to connect with consumers in more authentic and engaging ways. Acquired by Facebook in 2012, Instagram continues to be a dominant force in social media, shaping trends and cultural norms.
Reid Hoffman founded LinkedIn in 2002 with the goal of creating a professional networking platform. Unlike other social media sites focused on personal connections, LinkedIn was designed to connect professionals, facilitate job searches, and foster business relationships. The platform allows users to create professional profiles, network with colleagues, and share industry insights.
LinkedIn has become an indispensable tool for job seekers, recruiters, and businesses. It has transformed the job market by making it easier to find and connect with potential employers and employees. LinkedIn's influence extends beyond job searches; it has become a hub for professional development, thought leadership, and industry news. Hoffman's vision has significantly impacted how professionals manage their careers and build their networks.
Jan Koum and Brian Acton co-founded WhatsApp in 2009, aiming to create a simple, reliable..
Transforming the web into a real application platform
1. Transforming the Web into a RealApplication Platform:
NewTechnologies, EmergingTrends and Missing Pieces
Authors - Matti Anttonen, Arto Salminen, Tommi Mikkonen & Antero
Taivalsaari
Review by – Mohanadarshan Vivekanandalingam (148241N)
2. Contents
2
• What is meant by “Web as an application platform”
• Limitations in standalone applications
• History of Web
• Evolution of WWW
• New Technologies in Web
• HTML5, Javascript2, WebGL & etc…
• Other features in the Web
• Shortcoming of the Web
• Real-world examples
• Conclusion
3. Whatismeantby “Webasanapplicationsplatform”?
3
Using the Web as an applications platform means a site has opened its
applications interface -- at least in part -- to let third-party developers create
applets and other programs that make the site more user-friendly. The idea of
using the Web as an applications platform employs the concept of sharing
information to create a better and more useable product. In the case of Facebook,
for example, third-party developers have created thousands of applications that
make Facebook more enjoyable for its users.
5. Info.cern.ch was the address of the world’s first-ever web
site and web server, running on a NeXT computer at
CERN.
Tim Berners-Lee
History of Web
5
Beginning of Web
First website address - http://info.cern.ch/hypertext/WWW/TheProject.html
Source - http://www.designjuices.co.uk/2011/09/web-design-evolution/
6. History of Web
6
Stage- 1 (Early 1990)
Form-structured documents with only text and some static images
Mosaic is the only browser, It was the first web browser to allow pictures to appear inline with text, rather
than being opened in a separate tab.
7. History of Web(cont...)
7
Stage- 2 (Mid 1990)
Simple and Basic graphics
• The first hit counters began to appear at the bottom of websites.
• Designers put more focus on text color, which led to seizure-inducing text sites that excited visitors of the time.
8. History of Web(cont...)
8
Stage- 3 (Later1990)
Evolution of Flash
• User-accessible website creation software
• Most Interactive website user ever seen
9. History of Web(cont...)
9
Stage- 4 (In 2000)
Introduction of css & javscripts.
• Top navigation menus
• Drop down menus
• Web forms
10. History of Web(cont...)
10
Stage- 5 (Now)
Web 1.0 was all about connecting people. It was an interactive space, and I think Web 2.0 is, of course, a
piece of jargon, nobody even knows what it means. If Web 2.0 for you is blogs and wikis, then that is people
to people. But that was what the Web was supposed to be all along.” – Tim Berners-Lee, 2006
12. Contributionof W3C
12
Founded by Tim Berners-Lee in early 1990
• The World Wide Web Consortium (W3C) is the main international standards
organization for the World Wide Web
• Developing protocols and guidelines that ensure long-term growth for the
Web.
• W3C tries to enforce compatibility and agreement among industry members in
the adoption of new standards defined by the W3C. Incompatible versions of
HTML are offered by different vendors, causing inconsistency in how Web
pages are displayed. The consortium tries to get all those vendors to
implement a set of core principles and components which are chosen by the
consortium.
13. Why weneedstandardsinWeb?
13
• Achieve a More Stable Web
• Reduce Development and Maintenance Time
• Allow Backward Compatibility and Validation
• Increase Search Engine Success
• Graceful Degradation Now, and in the Future
• Common Knowledge
16. Javascript2
16
• OOP - Classes will be fully supported with all the inheritance properties found in classic Java or
C# languages.
• Strong Typing - JavaScript will be strong typed. This translates into the fact that any
declaration will be enforced, and not coerced to the platform engine. This closely resembles
ActionScript 3.0 syntax.
• Compile Time Type Checking - Developers will be able to request a “strict” mode compilation
that will perform several tasks and security checks before executing the code.
• Namespaces - Namespaces have been until now formed of global objects containing all the
necessary data needed for a JS application
• Constants - The “const” declaration has been introduced just to store constants that previously
relied on “var” declarations that could easily have been re-written by accident.
• Program Units - This requirement was introduced to minimize bandwidth usage. A program
unit in JavaScript 2.0 will store amounts of code that won't be used until called upon. It works
similarly to an ActionScript 3.0 library.
17. WebGL
17
• WebGL (Web Graphics Library) is a JavaScript API for rendering interactive 3D graphics and 2D
graphics within any compatible web browser without the use of plug-ins.
• WebGL brings 3D graphics to the Web by introducing an API that closely conforms to OpenGL
ES 2.0 that can be used in HTML5 <canvas> elements. Support for WebGL is present in Firefox
4+, Google Chrome 9+, Opera 12+, Safari 5.1+ and Internet Explorer 11+.
• WebGL does not have the fixed-function APIs introduced in OpenGL 1.0 and deprecated in
OpenGL 3.0. This functionality can instead be provided by the user in the JavaScript code space.
C3DL (http://www.c3dl.org/),
Copperlicht (http://www.ambiera.com/copperlicht/),
CubicVR (http://www.cubicvr.org/),
EnergizeGL (http://energize.cc/),
GLGE (http://www.glge.org/),
Framework that used webGL internally
WebGL specification - http://www.khronos.org/registry/webgl/specs/latest/2.0/
Check browser support - http://get.webgl.org/
18. Jaggaryjs
18
Jaggery is a framework to write webapps and HTTP-focused web services for all aspects of
the application: front-end, communication, Server-side logic and persistence in pure
Javascript. One of the intents of this framework is to reduce the gap between writing web
apps and web services. Importantly, Jaggery is open-source and released under Apache 2.0
More info - http://jaggeryjs.org/ & http://www.slideshare.net/nuwanbando/jaggery-introductory-webinar
A complete Javascript way to write all
parts of Web applications and services as
a way to reduce/eliminate impedance
mismatches across different layers of the
Web application and API development
experience.
19. Other Features inCurrent Web
19
Chrome browser & Chromium OS
• Chromium OS is a Linux-based operating system in which all the end user
applications are web applications.
• The only native application in the system is the web browser itself with support for
extensions and built-in media player. However, native code can be executed within
the browser with sandboxing technology called Native Client
Web Widget Runtimes
• This is different from general purpose web applications that do not require such
installation.
• In addition, web widget specifications have introduced bindings into the underlying
host operating system capabilities (device APIs), which in turn makes it possible to
access device resources, mobile device functions (such as SMS and MMS sending) and
even hardware peripherals and to combine these resources with web content.
20. Other Features inCurrent Web
20
Cloud Computing
• The actual computation takes place partially on the server side and partially on the
client side, depending of the specific needs of the applications and services.
• Cloud computing model makes it possible to utilize computing resources more
efficiently, and allows those resources to be shared between multiple sites
effortlessly, thereby converting capital expenditure into operational expenditure as
the customer does not need to own the hardware.
• Usually the services built on cloud infrastructure are accessed simply with a web
browser
21. Shortcomingsof theWeb
21
• User interaction issues
• Performance issues
• Networking and security issues
• Interoperability and compatibility issues
• Development and testing issues
• Deployment issues
23. EvaluationoncurrentWeb
23
User Interaction
• The lack of portable programmatic handling of features such as cut/copy/paste and drag-and-
drop used to be a significant problem for many web applications (Supported by HTML – drag
and drop)
• The presence of features that are semantically problematic for real applications, such as the
“back”, “forward” and “reload” buttons, still remains an issue in the web browser. (Alternative
custom-built native web client to access a service)
Performance
• The “browser performance wars”.
• High-performance JavaScript engines, raw JavaScript execution speed has increased by two
orders of magnitude compared to the situation only three years ago
• Availability of hardware accelerated graphics, there are still challenges when implementing
the Canvas API and WebGL efficiently
25. EvaluationoncurrentWeb
25
Security
• Yes, no much improvement in security aspect of the web.
• Chrome done a revolutionary here. Each browser tab is executed in a separate native (host
operating system) process. The isolation of individual tabs into different processes improves
browser security considerably, making it virtually impossible for one site to interfere with
code and content loaded from another site.
• Complement the existing domain-based browser security model with security permissions
and policies that would grant trusted sites/applications access to additional JavaScript APIs to
utilize host system capabilities
Compatibility
• Main bottleneck .
• The scope of the available JavaScript APIs is still limited.
• Standardization has progressed slowly and partly because some major browser vendors have
intentionally ignored the standards.
• Refusing to adopt new technologies.
26. AdvantagesofWebasanRealApplicationPlatform
26
• Reliability of the application - Applications and services consist of data, code and other resources
that can be located.
• Applications require no installation or manual upgrades. The user will simply click (or navigate
to) a link and the application or service will start running in the browser pretty much
immediately.
• Client machine environment will not affect the application much (sometimes browser
dependent).
• Web applications typically require no compilation, linking or static bindings
• Web apps can be tested part by part instead of writing thousands of code to deploy it.
• Development is further complicated by the fact that the JavaScript language was not originally
designed for use in large-scale applications.
28. Conclusion
28
• Web-based applications open up entirely new possibilities for software
development, and they can combine the best of both worlds.
• Transition towards web-based applications will mark the end of the era of
binary end user software.
• In the future, the use of conventional binary programs will be limited to
system software, while the vast majority of end user software will be
developed using web technologies.
• Web is the Future !.