Antoine of MMM#IM
Member
10mB for a page is a lot. If the page is really heavy on the graphics side, you might see something that high, but that is really, really a heavy page, lest its a dynamic page that is loading a ton from various databases (then size gets up there, but think pages like MySpace, and corporate intranets; normal web pages really aren't that large). Oh yea, Flash sites would qualify as sites that wouldnt't do well in this respect if they are 10+MB. That means a lot of entertainment sites with rich content might have an issue that's not just 'no FLash' related. But for the most part, there should not be issues.
Sounds like there is not much RAM to swap fun with. I am thinking no more than 64MB in there, maybe 128MBish; and much of that being taken up by the graphics, OS and touchscreen. Therefore only giving Safari 10MB to play with seems like a performance move.
In any case, does anyone think that the RAM won't be mentioned in final specs, I got a feeling that it will not be.
Sounds like there is not much RAM to swap fun with. I am thinking no more than 64MB in there, maybe 128MBish; and much of that being taken up by the graphics, OS and touchscreen. Therefore only giving Safari 10MB to play with seems like a performance move.
Sounds either like a new Flash plugin isn't ready, or Adobe might be demonstrating apps made using AIR. A few people might be able to pick that up quickly, hence a NDA to make sure that Adobe covers their's.Everyone in attendance will be asked to sign a brief Non-Disclosure Agreement, either electronically or on paper. This agreement is in place to protect attendees in case they are exposed to any confidential information from Adobe. We do not anticipate that attendees will be exposed to Adobe Confidential information, but the NDA is required for admittance, and only applies to Adobe Proprietary Information. See iPhoneDevCampAdobeNDA.
With the exception of some of that "design for the iPhone junk' much of this isn't much different from modern [professional] coding. It's good to see Apple pushing some semblance of using standards and best practices. However, sounds like Safari 3 for the iPhone does do a bit of optimization onboard (similar to Blazer and its optimized mode) and hence some of the issues. I think that if enough people visit certain sites on the iPhone, those sites would be updated so that no 'iPhone specific' considerations need to be made. Though this does seem like the iPhone might choke some on table-based designs. Good. Best to ditch that antiquated type of designing anywaysSeparate HTML and CSS
Use well structured and valid HTML
Size images appropriately dont rely on browser scaling
Tile small images in backgrounds, dont use large background images
iPhone supports both EDGE and Wi-Fi.
EDGE pipe is smaller than Wi-Fi pipe, so consider bandwidth when developing.
XHTML mobile documents supported
Stylesheet device width: 480px
Apply different CSS for the iPhone.
For example displaying a one column page for iPhone vs. a 3 column page on a desktop.
There are no scroll bars or resize knobs.
The iPhone will automatically expand the content.
Avoid framesets. Scrollable frames are automatically expanded to fit the content
iPhone User Agent: Mozilla/5.0 (iPhone; U; CPU like Mac OS X; en) AppleWebKit/420+ (KHTML, like Gecko) Version/3.0 Mobile/1A538a Safari/419.3
Video: H.264 baseline profile level 3.0 up to 640x480 fps
Honestly, if every browser (desktop and mobile) enforced this, the web would be a much nicer place. Nevertheless, sounds like the Webkit engine might not have enough horsepower behind it to push this more without some kind of performance hit to the entire system. So the suggestion to throttle back the pages, instead of beefing up the hardware to compensate. Tis a shame Palm couldn't pull that line off with the Foleo, because similar would be the case there too.10MB max html size for web page
Javascript limited to 5 seconds run time (for comparison, Firefox has a 10 second limitation)
Javascript allocations limited to 10MB (like pages)
In any case, does anyone think that the RAM won't be mentioned in final specs, I got a feeling that it will not be.