CompetitiveBrowserDevelopment: Difference between revisions
Jump to navigation
Jump to search
| Line 8: | Line 8: | ||
| <b> Future Version </b> || 8.0 | | <b> Future Version </b> || 8.0 | ||
|- | |- | ||
| <b> Release Date </b> || [http://news.softpedia.com/news/Firefox-3-0-Drops-in-2007-Internet-Explorer-8-0-Maybe-in-2008-53824.shtml end of 2008 or 2009]; Beta in 2007, released after Vista SP1 | | <b> Release Date </b> || [http://news.softpedia.com/news/Firefox-3-0-Drops-in-2007-Internet-Explorer-8-0-Maybe-in-2008-53824.shtml end of 2008 or 2009]; [http://www.tech.co.uk/computing/internet-and-broadband/news/microsoft-ie8-trial-coming-soon?articleid=1339033012 Beta in 2007, released after Vista SP1] | ||
|} | |} | ||
Revision as of 17:21, 25 June 2007
Internet Explorer
| Web Browser | Internet Explorer |
| Current Version | 7.0 |
| Future Version | 8.0 |
| Release Date | end of 2008 or 2009; Beta in 2007, released after Vista SP1 |
Direction
- new client scripting APIs
- standards compliance
- usability
- security
- support for growing uses of the Web (blogs, etc.)
- unofficial: IE browser for XBox 360 [1]
Emphasis
- security
- standards compliance: layout, more compliant w/ CSS 2.1 layout standards, increased compliance w/ Object Model, allow more flexible programming patterns; more client-side APIs for Ajax (like local storage and mashup security model)
- make the IE 8.0 object model more interoperable with that used by other browsers
- allow developers to more easily add extensions to its browser
- invest heavily in advancing its Web development toolbar with the next version of IE
Features
- require Web site authors to "opt-in" to standards mode when developing IE 8.0 sites: authors then have to take responsibility for breaking pages
- improved APIs for client-side scripting, particularly to support AJAX applications, such as Outlook Web Access and Google Maps - this API could help AJAX applicaitons to operate reliably offline
- enable browser scripts to save data into a limited-capacity, restricted store on the client
- improved security model to support local storage and "mashup" sites
- implementation of W3C's client-side event API
- Support for CardSpace and microformats
Possible Features
- implement the HTML 5 standards
- Online/Offline RSS Feeds and Reader
- Improved Bookmark Management
- "Locking" a page to prevent users from accidentally navigating away from it
- Adding a "Find on Page" capability
- Improving username/password management
- Restoring the "Image Toolbar" provided in earlier IE 7 test builds
- Changing the download mechanism, perhaps eliminating the initial download to the "temporary Internet files" folder; download manager that can continue downloads across multiple sessions
- Adding easily editable config files (similar to Firefox's userChrome.css and UserContent.css)
- Enabling draggable tabs from one IE window to another
- Configuring tabs so that each has its own private cookie cache
- Introducing new status bar info, possibly with fields such as "last accessed by user" and "window last updated"
- Enabling add-ons, such as stocks, movies, etc., a la Firefox
- UI: a hybrid of the tradition browser UI and the Office Ribbon. When visiting certain websites the UI morphs to display new buttons and options. For example when you visit MSN Soapbox, a button that allows you to upload videos, appears on the toolbar.
- Semantics: focus on context rather than just content. When you go to a website, IE8 scans and analyzes the content of the page to find out what the page is about, and then looks for additional information, whether it be ratings for a movie or the download link for a software. The retrieved information can be viewed in the sidebar, a new tab, or a pop-up window. It is also extensible so, although by default when you go to a page about a movie, you get information from IMDB only, with third party add-ons, you can can add that movie in your NetFlix cue, buy it from Amazon or eBay, or simply download it using BitTorrent.
Challenges
- security
- compatibility vs. standards-compliance: don't want to break existing sites without solid reasons
Strengths
- Browser pre-installed, default for all XP, Vista computers; many users don't know about the availability of other web browsers, and simply use what is already in front of them
- Market share: 79%
- Developers optimize and test their sites against IE (Compatibility/Site Rendering)
- Inherently easier to integrate with MS Office, Windows, and the XBox 360
Weaknesses
- Target for hackers
- Perceived as slower and more bloated
- Perceived as being less secure
Safari
| Web Browser | Safari |
| Current Version | 2.0 |
| Future Version | 3.0 |
| Release Date | October 2007 |
Direction
- Expand browser market share; more web site developers will test their code against Safari, which is good for Apple
- Save Quicktime; better quicktime integration into Safari for Windows
- iPhone - get Mac and Windows developers to develop web apps for iPhone.
- increase search box revenue
- using iTunes as a distribution vehicle for Safari for Windows
Emphasis
- speed/performance
- easy to use
- Safari for Windows
Features
- Safari on the iPhone: links can be embedded in web pages to allow phone calls from a click (source: arstechnica.com)
- photographs with richer, deeper colors [2]
- anti phishing: automatically detecting "phishy" or deceitful website URLs. It then notifies the user via a dialog box, webpage overlay, or a combination of the two.
- significant user interface changes to iCal, 3D audio cues in VoiceOver, live previews in print panels, basic document editing in Preview.app, and the ability to restore groups and subgroups in AddressBook with Time Machine.
- support for PDF, HTML, Web Archives, Text, QuickTime movies and sound in "Quick Look" view
- (unofficial): access Google's AntiTrust database through a plug-in or under-the-hood extension for anti phishing
- (unofficial): allow its iPhoto digital photo cataloging application to interact with Google's Maps service.
- Web Clip
- Manipulatable browser tabs: ability to reorder tabs through drag-and-drop; ability to drag individual tabs off an existing browser window, thus creating a fresh browser window with the contents of that tab; ability to drag tabbed windows from one Safari window to another, or ask the browser to consolidate all open windows into one, making tabs for each existing page in a single Safari browser window.
- In-page lightbox searching: in-page searching that allows users search "live" for specific search terms on any web page; find all instances of the search term right off the bat; implements the "lightbox" technique it invented for Dashboard, dimming the web page background and shinning a spotlight on the text matches.
- Resizable text areas: Web designers developing pages for Safari will no longer have to fiddle with TEXTAREA form elements in order to satisfy user requirements, while at the same time maintaining some semblence of good page design; enables a "resize" corner that allows users to resize text fields on a web page in real time, to suit their text-editing needs.
- easy view of all your plug-ins
- ability for private browsing - information about an individual's browsing history isn't stored
- SnapBack: one-click access to an initial search query
Challenges
- Safari is optimized for Macs; it will take time for Safari for Windows to stabilize and catch up to the other Windows browsers
- Window’s-based malware and security issues
- Mobile developers were disappointed about not having the ability to design native apps (no Software Development Kit, but devs can create Web 2.0 apps that run w/in iPhone’s version of Safari using tools like Ajax); opening up 3rd-party development threatens security and reliability of phone
- More resources needed to support more platforms
Strengths
- Perceived coolness factor
- Perceived ease of use
- Mac default web browser
Weaknesses
- Not yet secure on Windows
- Not yet stable on Windows - website won't look/work right
- Plug-in support is non-existent
Opera
| Web Browser | Opera |
| Current Version | 9.21 |
| Future Version | 9.5, 10.0 |
| Release Date | 9.5 in 2007; first preview of 10.0 at the end of 2007 |
Direction
- cross-platform experience
- tools providing open standard development platform
- collaboration with some Linux distributions on including Opera
- facilitating easier browsing on cell phones, such as entering long URLs
Emphasis
- css selectors
- increase user base, spread word about Opera
Features
- cross platform experience - allow user to begin reading a web page on the desktop, then continue on a mobile phone or PDA
- native video functionality for mobile browser that will replace Adobe Flash plug-in
- open standard development platform
- support more CSS3 selectors; how HTML tags behave depending on hierarchy
- text-shadow property
- bug fixes to standards support
- screen reader support
- new rendering improvements
- works on non-traditional platforms - Nintendo DS and Wii
Challenges
- gaining popularity
- not open source; some Linux distributions won’t include Opera for this reason
- increasing awareness about the browser
Strengths
- Many Linux Distributions already include Opera: Ubuntu, Arabian Linux (Opera), Arch, Buffalo Linux, Gentoo, Linspire, Lunar Linux, Lycoris (now Mandriva), Mandriva, MCNLive, Mustang, Red Flag, SUSE, Puppy, Feather, RR4, AUSTRUMI, Turbo Linux, Xandros, Vector linux (deluxe), phones, devices, and more
- Speed
- Best compliance to web standards (acid2 test)
- Mobile platforms: cell phones, Nintendo Wii, Nintendo DS
Weaknesses
- Lack of awareness
- Some web pages don't render on Opera as many webmasters don't test this browser