WebKit deals in logical pixels and a device pixel ratio to render stuff. It knows nothing about the physical pixels of the display. So when you really have 640x960 pixels on the display, your iPhone's Safari will tell you that you have 320x480 pixels to work with a device pixel ratio of 2. If you try to supply an image without any hints, it'll try to render the image at 1x scale in twice the width/height you want (which will be upscaled). However you can give it some hints to tell it what to render at. And this technique is applicable both to iOS devices (which have 1x and 2x scale devices) an
WebKit deals in logical pixels and a device pixel ratio to render stuff. It knows nothing about the physical pixels of the display. So when you really have 640x960 pixels on the display, your iPhone's Safari will tell you that you have 320x480 pixels to work with a device pixel ratio of 2. If you try to supply an image without any hints, it'll try to render the image at 1x scale in twice the width/height you want (which will be upscaled). However you can give it some hints to tell it what to render at. And this technique is applicable both to iOS devices (which have 1x and 2x scale devices) and Android devices (which have 0.75x, 1x, 1.5x, and 2x scale devices).
Let's pretend you have a source image that is 200x200 at 1x scale, and 400x400 at 2x scale.
If you'd like to use <img> tags to render images, you can pass your 2x scale image as the src, as long as you set the width/height to 200x200 (either as tag attributes or as CSS styles). This is generally not preferable, as you can't really differentiate between different scaled devices this way (unless you're using JavaScript, and at that point you might as well use the next technique). But if you only want to make one asset one time, and don't mind the extra bandwidth, you can use this approach.
The best approach is to use CSS background and background-image to supply your images. The trick here is to use the CSS background-size property to set the render size of the image at 1x (in this case, background-size: 200px 200px). You can combine this with CSS background-position to achieve sprited assets (where you put all your images into one giant image and slice out the relevant parts of it).
The big advantage here is that you can target specific screen scale factors with CSS, using a trick known as CSS media queries. This lets you specify entire CSS files, or parts of CSS files, to load for devices at 1x scale, at 2x scale, and other scales (as well as ranges of scales). This means that 1x scale devices are only loading 1x assets, and 2x scale devices are only loading 2x scale assets. The best way to do this is split your assets into multiple CSS files, and load them using the media attribute, like so:
<link rel="stylesheet" href="1x.css" media="only screen and (-webkit-device-pixel-ratio: 1)" />
<link rel="stylesheet" href="2x.css" media="only screen and (-webkit-device-pixel-ratio: 2)" />
You can also do this in one CSS file like so:
@media only screen and (-webkit-device-pixel-ratio: 1){
.image{ ... }
}
@media only screen and (-webkit-device-pixel-ratio: 2){
.image{ ... }
}
There are also -webkit-min-device-pixel-ratio and -webkit-max-device-pixel-ratio selectors you can use, so you can use specific assets for a range of device pixel ratios (which matters if you're targeting Android). The scaling will Just Work across all device pixel ratios when you do this.
You can also query for this property in JavaScript. window.devicePixelRatio will return 1 for 1x scale, 1.5 for 1.5x, 2 for 2x, etc.
UPDATE: As of iOS 5.1, it appears there is an issue with high-resolution JPG images being presented in this manner. WebKit on Retina iPads will downscale the image and then upscale it again, leading to a significantly uglier image. The only known workaround is to use PNG images instead of JPGs (which obviously sucks for high-resolution images, which consume significantly more bandwidth than JPGs). Apple has been made aware of this issue: rdar://problem/11097671. If your image contains greater than 2 * 1024 * 1024 (2097152) pixels when you multiply the width and height together, you must use PNGs, or the image will not appear crisp on the Retina display.
UPDATE 2: There is supposedly a way to work around this, by saving JPEGs in Progressive mode. There is a "Progressive" checkbox in Photoshop's Save For Web which enables this. I haven't tested this myself, but multiple people have reported that it works. Thanks to Iain Anderson in the comments below, as well as codezero on Hacker News.
Where do I start?
I’m a huge financial nerd, and have spent an embarrassing amount of time talking to people about their money habits.
Here are the biggest mistakes people are making and how to fix them:
Not having a separate high interest savings account
Having a separate account allows you to see the results of all your hard work and keep your money separate so you're less tempted to spend it.
Plus with rates above 5.00%, the interest you can earn compared to most banks really adds up.
Here is a list of the top savings accounts available today. Deposit $5 before moving on because this is one of th
Where do I start?
I’m a huge financial nerd, and have spent an embarrassing amount of time talking to people about their money habits.
Here are the biggest mistakes people are making and how to fix them:
Not having a separate high interest savings account
Having a separate account allows you to see the results of all your hard work and keep your money separate so you're less tempted to spend it.
Plus with rates above 5.00%, the interest you can earn compared to most banks really adds up.
Here is a list of the top savings accounts available today. Deposit $5 before moving on because this is one of the biggest mistakes and easiest ones to fix.
Overpaying on car insurance
You’ve heard it a million times before, but the average American family still overspends by $417/year on car insurance.
If you’ve been with the same insurer for years, chances are you are one of them.
Pull up Coverage.com, a free site that will compare prices for you, answer the questions on the page, and it will show you how much you could be saving.
That’s it. You’ll likely be saving a bunch of money. Here’s a link to give it a try.
Consistently being in debt
If you’ve got $10K+ in debt (credit cards…medical bills…anything really) you could use a debt relief program and potentially reduce by over 20%.
Here’s how to see if you qualify:
Head over to this Debt Relief comparison website here, then simply answer the questions to see if you qualify.
It’s as simple as that. You’ll likely end up paying less than you owed before and you could be debt free in as little as 2 years.
Missing out on free money to invest
It’s no secret that millionaires love investing, but for the rest of us, it can seem out of reach.
Times have changed. There are a number of investing platforms that will give you a bonus to open an account and get started. All you have to do is open the account and invest at least $25, and you could get up to $1000 in bonus.
Pretty sweet deal right? Here is a link to some of the best options.
Having bad credit
A low credit score can come back to bite you in so many ways in the future.
From that next rental application to getting approved for any type of loan or credit card, if you have a bad history with credit, the good news is you can fix it.
Head over to BankRate.com and answer a few questions to see if you qualify. It only takes a few minutes and could save you from a major upset down the line.
How to get started
Hope this helps! Here are the links to get started:
Have a separate savings account
Stop overpaying for car insurance
Finally get out of debt
Start investing with a free bonus
Fix your credit
Making your app ready for Retina displays doesn’t have to be a hassle. Whether you are building a new app or upgrade an existing one, this guide is designed to help you get the job done smoothly.
Make it Retina first
The easiest and most time-saving way to add retina support is to create one image that is optimized for retina devices and serve it to non-retina devices as well.
By now every modern browser uses bicubic resampling and does a great job with downsampling images. Here is a comparison of downsampling in Photoshop vs Google Chrome using an image from our Growth Engineering 101 website.
T
Making your app ready for Retina displays doesn’t have to be a hassle. Whether you are building a new app or upgrade an existing one, this guide is designed to help you get the job done smoothly.
Make it Retina first
The easiest and most time-saving way to add retina support is to create one image that is optimized for retina devices and serve it to non-retina devices as well.
By now every modern browser uses bicubic resampling and does a great job with downsampling images. Here is a comparison of downsampling in Photoshop vs Google Chrome using an image from our Growth Engineering 101 website.
There are two ways to let the browser downsample images for you. Using img tags and using CSS background images.
If you have img tags serve the retina optimized image and set the width and height attributes to half of the resolution of the actual image (e.g. 400x300 if the image dimensions are 800x600).
- <img src=”http://www.example.com/retina-image-800x600-2x.png” width=”400” height=”300”>
If you use images as CSS background you can use the background-size property of CSS3 to downsample the image for non-retina devices.
<div class=”photo”></div>
.photo { background-image: url(retina-image-800x600-2x.png); background-size: 400px 300px; background-repeat: no-repeat; display: block; width: 400px; height: 300px; }
In both cases make sure to use even numbers in both dimensions to prevent displacement of pixels when the image is being downsampled by the browser.
When downsampling is not good enough
Usually browser downsampling should work very well. That said there are some situations where downsampling in the browser might make images blurry.
Here we have a bunch of 32x32 px social icons.
And here is how they look like downsampled to 16x16px by Photoshop’s as well as Google Chrome’s bicubic filter. It seems like we get better results from Photoshop in this case.
To get the best results for our users we can create two versions of the same image. One for retina devices and another one downsampled by photoshop for non-retina devices.
Now you can use a CSS media query to serve retina or non-retina images depending on the pixel density of the device.
- /* CSS for devices with normal screens */ .icons { background-image: url(icon-sprite.png); background-repeat: no-repeat; } /* CSS for high-resolution devices */ @media only screen and (-Webkit-min-device-pixel-ratio: 1.5), only screen and (-moz-min-device-pixel-ratio: 1.5), only screen and (-o-min-device-pixel-ratio: 3/2), only screen and (min-device-pixel-ratio: 1.5) { .icons { background-image: url(icon-sprite-2x.png); background-size: 200px 100px; background-repeat: no-repeat; } }
If you use a background color for small icons on the other hand, downsampling by the browser works pretty well. This is the same downsampling example with white background.
Polishing your Downsampled Images
If you’re still not satisfied with the results from Photoshop’s downsampling you can go the extra mile and hand-optimize the non-retina version to get super crisp results.
Below are some examples of images from the Blossom product website that I hand-optimized for people on non-retina devices.
Borders & Strokes
Here is an example of downsampling issues with hairlines where I re-draw the lines of the downsampled image.
View the Retina Version of this Image on Dribbble.
Text
Here is an example of downsampling issues with text. In this case I manually re-wrote the text “Feature Pipeline” to get to a crisp result.
The Image above is the Retina Version
When details, crisp fonts and clean hairlines are important you might want to go the extra mile.
Try to avoid Images
The main disadvantages of rasterized images are their big file size and that they don’t scale well to different sizes without affecting the image quality. Great alternatives to rasterized graphics are CSS, Scalable Vector Graphics (SVG) and Icon Fonts.
If you have any chance to build graphical elements of your app in CSS go for it. You can use it to add gradients, borders, rounded corners, shadows, arrows, rotate elements and much more.
Here are a few examples of interaction elements in Blossom that are implemented in CSS. The subtle gradient is powered by CSS gradients and the custom font in use on this button is Kievit served via Typekit. No images.
In the following screenshot the only two images used are the user avatar and the blue stamp. Everything else – the circled question mark, the dark grey arrow next to it, the popover, its shadow and the arrow on top of it are all pure HTML and CSS.
Here you can see how projects in Blossom look like. It’s a screenshot of a project’s website used as cover on a stack of paper sheets. The paper sheets are implemented with divs that are rotated using CSS.
Also the circled arrow in the righthand side of the screenshot below is pure CSS.
Here are some awesome tools that can help you to save time when you are creating effects using CSS.
CSS Generator:
Cross browser CSS3 syntax by @RandyJensen.
CSS3Generator by @RandyJensen
CSS Arrows:
CSS for tooltip arrows by @ShojBerg.
cssarrowplease
Generating CSS for Sprites:
Sprite Cow helps you get the background-position, width and height of sprites within a spritesheet as a nice bit of copyable css. It’s built by TheTeam and it’s a real time saver and definitely worth giving a try.
Generate CSS for sprite sheets
The main advantage of SVG is that unlike rasterized graphics they scale reasonably well to various sizes. If you have simple shapes they usually are also way smaller than PNGs and are often used for things like charts.
Icon Fonts are often used as a replacement for image sprites. Similar to SVG they can be scaled up infinitely without any loss of quality and are usually smaller in size compared to image sprites. On top of that you can use CSS to change their size, color and even add effects like shadows.
Both SVG and Icon Fonts are well supported by modern browsers.
Retina ready Favicons
Favicons are really important for users who want to have an overview about which app belongs to which browser tab. A Retina ready Favicon will not only be easier to identify but also stand out among a crowd of Favicons that are not optimized for high resolution devices yet.
To make your Favicon Retina ready I can highly recommend X-Icon Editor. You can either upload a single image and let the editor resize it for different dimensions or you can upload separate images optimized for each size to get the best results.
How to make existing Images Retina ready
If you want to upgrade an app with existing images it is a bit more work as you need to re-create all images to make them Retina ready but this doesn’t need to be super hard.
First of all try to identify images that you can avoid by using alternatives like CSS, SVG and Image Fonts as mentioned previously. Buttons, Icons and other common UI widgets usually can be replaced with modern solutions that don’t require any images.
In case you actually need to re-create rasterized images you need to go back to your source files. As you might assume, simply resizing your rasterized bitmap images twice as big doesn’t get the job done because all the details and borders get pixelated.
But no need to despair – image compositions which mostly contain vectors i.e. in Adobe Photoshop or Illustrator are quite easy to scale up. That said don’t forget to check if your Photoshop effects in the blending options such as strokes, shadows and bevels still look as intended.
In general, making most Photoshop Compositions directly out of vectors (shapes) and Photoshop’s Smart Objects will save you a lot of time in the future.
How to optimize the File Size of Images
Last but not least optimizing the file size of all images in an application or website could effectively save up to 90% of image loading times. When it comes to retina images, the file size reduction gets even more important as they have a higher pixel density which also increases their file size.
In Photoshop you can optimize the image filesize via the “Save for Web” feature. On top of that there is an amazing free tool called ImageAlpha, which can reduce the filesize of your images even more with just a minor loss of quality.
Unlike with Photoshop you can use ImageApha to convert 24-bit alpha channel PNGs to 8-bit PNGs with alpha channel support. The icing on the cake is that these optimized images are cross-browser compatible and even work for IE6.
You can play around with different settings in ImageAlpha to get the right trade-off between quality and file-size. In the case below we can reduce the file size by almost 80%.
When you are done setting your desired compression levels ImageAlpha’s save dialog also offers you to “Optimize with ImageOptim” - another awesome free tool.
ImageOptim automatically picks the best compression options for your image and removes unnecessary meta information and color profiles. In the case of our stamp file ImageOptim was able to reduce our file size by another 34%.
After we’ve updated all assets of Blossom for high resolution displays and used ImageAlpha & ImageOptim to optimize the file size we actually ended up saving a few kb in comparison to the assets we had before.
Save Time, read this Book
If you want to learn more about how to get your apps ready for retina displays I can highly recommend "Retinafy your web sites & apps" by Thomas Fuchs. It’s a straightforward step by step guide which saved me a lot of time and nerves
Awesome Retina Ready Sites on the Web
Simple version control for designers
Panic - Shockingly Good Software.
You can find the Blog Version of this Post here:
http://www.allanberger.com/post/49938151321/how-to-make-your-apps-retina-ready
While css background images are great for cosmetic images like page backgrounds or icon sprites, it's not a good idea to use this technique for important content images since background images don't print. Of course, I'd be surprised if any iPad user prints anything; however, it's still a common practice for many traditional computer users (e.g., people who find reading on paper easier and desktop PC users who want info on the go). For this reason, I never serve any important content images or logos as background images.
As a result, no one way is the best approach. Likely we will need to use a
While css background images are great for cosmetic images like page backgrounds or icon sprites, it's not a good idea to use this technique for important content images since background images don't print. Of course, I'd be surprised if any iPad user prints anything; however, it's still a common practice for many traditional computer users (e.g., people who find reading on paper easier and desktop PC users who want info on the go). For this reason, I never serve any important content images or logos as background images.
As a result, no one way is the best approach. Likely we will need to use a combination of approaches depending on the image and it's use:
- Page backgrounds and icon sprites — css background images and media queries.*
- Logos and other graphics/images that need to be printable — server-side detection or client side javascript or if it's a small image you could be lazy and just serve high res by default.
In an ideal world, the W3C proposed <picture> element would already be part of HTML5 (for info on this see the Responsive Images Community Group: http://www.w3.org/community/respimg/). Since this isn't happening any time soon, it's down to either server-side or client-side detection. On the client-side, the two options I know are:
- the already mentioned jQuery Retina plugin: http://troymcilvena.com/post/998277515/jquery-retina
- or the PictureFill which uses javascript to add support for the proposed picture element: https://github.com/scottjehl/picturefill
*Bonus Answer on icons: If you are using lots of icons instead of css sprites you should look into using icon fonts. There is a good write-up here on the technique: http://somerandomdude.com/2010/05/04/font-embedding-icons/ There are a number of icon fonts out there that you can use like Fontomas: http://nodeca.github.com/fontomas/ and Font Awesome: http://fortawesome.github.com/Font-Awesome/ and Pictos: http://pictos.cc/
If you're willing to use the background-image CSS property rather than a typical img element with src attribute, there is a very elegant method to serve images that is supported by the latest webkit browsers (the new iPad's Safari browser qualifies):
Images in CSS — Web Fundamentals
Here's a quick and dirty SCSS mixin that loads only the appropriate image for a given device, with a fallback for unsupported browsers to simply load the 1x image:
@mixin image-set($image1x, $image2x, $repeat: 'no-repeat') {
background-image: url($image1x);
background-image: -webkit-image-set(
url($image1x) 1x
If you're willing to use the background-image CSS property rather than a typical img element with src attribute, there is a very elegant method to serve images that is supported by the latest webkit browsers (the new iPad's Safari browser qualifies):
Images in CSS — Web Fundamentals
Here's a quick and dirty SCSS mixin that loads only the appropriate image for a given device, with a fallback for unsupported browsers to simply load the 1x image:
@mixin image-set($image1x, $image2x, $repeat: 'no-repeat') {
background-image: url($image1x);
background-image: -webkit-image-set(
url($image1x) 1x,
url($image2x) 2x
);
background-image: image-set(
url($image1x) 1x,
url($image2x) 2x
);
background-repeat: unquote($repeat);
}
Just drop it into your code and use it like this:
.img-i-want-to-make-2x-enabled {
@include image-set('image.png', 'image@2x.png');
}
With today’s modern day tools there can be an overwhelming amount of tools to choose from to build your own website. It’s important to keep in mind these considerations when deciding on which is the right fit for you including ease of use, SEO controls, high performance hosting, flexible content management tools and scalability. Webflow allows you to build with the power of code — without writing any.
You can take control of HTML5, CSS3, and JavaScript in a completely visual canvas — and let Webflow translate your design into clean, semantic code that’s ready to publish to the web, or hand off
With today’s modern day tools there can be an overwhelming amount of tools to choose from to build your own website. It’s important to keep in mind these considerations when deciding on which is the right fit for you including ease of use, SEO controls, high performance hosting, flexible content management tools and scalability. Webflow allows you to build with the power of code — without writing any.
You can take control of HTML5, CSS3, and JavaScript in a completely visual canvas — and let Webflow translate your design into clean, semantic code that’s ready to publish to the web, or hand off to developers.
If you prefer more customization you can also expand the power of Webflow by adding custom code on the page, in the <head>, or before the </head> of any page.
Trusted by over 60,000+ freelancers and agencies, explore Webflow features including:
- Designer: The power of CSS, HTML, and Javascript in a visual canvas.
- CMS: Define your own content structure, and design with real data.
- Interactions: Build websites interactions and animations visually.
- SEO: Optimize your website with controls, hosting and flexible tools.
- Hosting: Set up lightning-fast managed hosting in just a few clicks.
- Grid: Build smart, responsive, CSS grid-powered layouts in Webflow visually.
Discover why our global customers love and use Webflow | Create a custom website.
An oft-overlooked solution is to use the CSS "content" property in combination with the "-webkit-image-set" construct. This lets you control an <img> element's source from CSS like so:
- #someImgElement {
- content: -webkit-image-set(url(foo.png) 1x, url(foo@2x.png) 2x);
- }
We use this technique all over the place in the WebKit Web Inspector codebase.
David Kaneda (Sencha) posted a good article on this: http://www.sencha.com/blog/2010/08/23/resolution-independent-mobile-ui/. A basic short answer is use as many CSS effects as you dare and SVG images as opposed to bitmap (PNG, JPG, GIF). But be careful, the new stuff doesn't work on every browser so you should degrade gracefully.
I once met a man who drove a modest Toyota Corolla, wore beat-up sneakers, and looked like he’d lived the same way for decades. But what really caught my attention was when he casually mentioned he was retired at 45 with more money than he could ever spend. I couldn’t help but ask, “How did you do it?”
He smiled and said, “The secret to saving money is knowing where to look for the waste—and car insurance is one of the easiest places to start.”
He then walked me through a few strategies that I’d never thought of before. Here’s what I learned:
1. Make insurance companies fight for your business
Mos
I once met a man who drove a modest Toyota Corolla, wore beat-up sneakers, and looked like he’d lived the same way for decades. But what really caught my attention was when he casually mentioned he was retired at 45 with more money than he could ever spend. I couldn’t help but ask, “How did you do it?”
He smiled and said, “The secret to saving money is knowing where to look for the waste—and car insurance is one of the easiest places to start.”
He then walked me through a few strategies that I’d never thought of before. Here’s what I learned:
1. Make insurance companies fight for your business
Most people just stick with the same insurer year after year, but that’s what the companies are counting on. This guy used tools like Coverage.com to compare rates every time his policy came up for renewal. It only took him a few minutes, and he said he’d saved hundreds each year by letting insurers compete for his business.
Click here to try Coverage.com and see how much you could save today.
2. Take advantage of safe driver programs
He mentioned that some companies reward good drivers with significant discounts. By signing up for a program that tracked his driving habits for just a month, he qualified for a lower rate. “It’s like a test where you already know the answers,” he joked.
You can find a list of insurance companies offering safe driver discounts here and start saving on your next policy.
3. Bundle your policies
He bundled his auto insurance with his home insurance and saved big. “Most companies will give you a discount if you combine your policies with them. It’s easy money,” he explained. If you haven’t bundled yet, ask your insurer what discounts they offer—or look for new ones that do.
4. Drop coverage you don’t need
He also emphasized reassessing coverage every year. If your car isn’t worth much anymore, it might be time to drop collision or comprehensive coverage. “You shouldn’t be paying more to insure the car than it’s worth,” he said.
5. Look for hidden fees or overpriced add-ons
One of his final tips was to avoid extras like roadside assistance, which can often be purchased elsewhere for less. “It’s those little fees you don’t think about that add up,” he warned.
The Secret? Stop Overpaying
The real “secret” isn’t about cutting corners—it’s about being proactive. Car insurance companies are counting on you to stay complacent, but with tools like Coverage.com and a little effort, you can make sure you’re only paying for what you need—and saving hundreds in the process.
If you’re ready to start saving, take a moment to:
- Compare rates now on Coverage.com
- Check if you qualify for safe driver discounts
- Reevaluate your coverage today
Saving money on auto insurance doesn’t have to be complicated—you just have to know where to look. If you'd like to support my work, feel free to use the links in this post—they help me continue creating valuable content.
Here's a new one:
retina.js
http://retinajs.com/
I quite like the foresight.js method of detecting image rendering capability's and serving the relevant image. Also has the bonus of detecting connection speed too which is useful in this day and age of less than ideal mobile broadband speed. Have a look at it here: https://github.com/adamdbradley/foresight.js
Here’s the thing: I wish I had known these money secrets sooner. They’ve helped so many people save hundreds, secure their family’s future, and grow their bank accounts—myself included.
And honestly? Putting them to use was way easier than I expected. I bet you can knock out at least three or four of these right now—yes, even from your phone.
Don’t wait like I did. Go ahead and start using these money secrets today!
1. Cancel Your Car Insurance
You might not even realize it, but your car insurance company is probably overcharging you. In fact, they’re kind of counting on you not noticing. Luckily,
Here’s the thing: I wish I had known these money secrets sooner. They’ve helped so many people save hundreds, secure their family’s future, and grow their bank accounts—myself included.
And honestly? Putting them to use was way easier than I expected. I bet you can knock out at least three or four of these right now—yes, even from your phone.
Don’t wait like I did. Go ahead and start using these money secrets today!
1. Cancel Your Car Insurance
You might not even realize it, but your car insurance company is probably overcharging you. In fact, they’re kind of counting on you not noticing. Luckily, this problem is easy to fix.
Don’t waste your time browsing insurance sites for a better deal. A company called Insurify shows you all your options at once — people who do this save up to $996 per year.
If you tell them a bit about yourself and your vehicle, they’ll send you personalized quotes so you can compare them and find the best one for you.
Tired of overpaying for car insurance? It takes just five minutes to compare your options with Insurify and see how much you could save on car insurance.
2. Ask This Company to Get a Big Chunk of Your Debt Forgiven
A company called National Debt Relief could convince your lenders to simply get rid of a big chunk of what you owe. No bankruptcy, no loans — you don’t even need to have good credit.
If you owe at least $10,000 in unsecured debt (credit card debt, personal loans, medical bills, etc.), National Debt Relief’s experts will build you a monthly payment plan. As your payments add up, they negotiate with your creditors to reduce the amount you owe. You then pay off the rest in a lump sum.
On average, you could become debt-free within 24 to 48 months. It takes less than a minute to sign up and see how much debt you could get rid of.
3. You Can Become a Real Estate Investor for as Little as $10
Take a look at some of the world’s wealthiest people. What do they have in common? Many invest in large private real estate deals. And here’s the thing: There’s no reason you can’t, too — for as little as $10.
An investment called the Fundrise Flagship Fund lets you get started in the world of real estate by giving you access to a low-cost, diversified portfolio of private real estate. The best part? You don’t have to be the landlord. The Flagship Fund does all the heavy lifting.
With an initial investment as low as $10, your money will be invested in the Fund, which already owns more than $1 billion worth of real estate around the country, from apartment complexes to the thriving housing rental market to larger last-mile e-commerce logistics centers.
Want to invest more? Many investors choose to invest $1,000 or more. This is a Fund that can fit any type of investor’s needs. Once invested, you can track your performance from your phone and watch as properties are acquired, improved, and operated. As properties generate cash flow, you could earn money through quarterly dividend payments. And over time, you could earn money off the potential appreciation of the properties.
So if you want to get started in the world of real-estate investing, it takes just a few minutes to sign up and create an account with the Fundrise Flagship Fund.
This is a paid advertisement. Carefully consider the investment objectives, risks, charges and expenses of the Fundrise Real Estate Fund before investing. This and other information can be found in the Fund’s prospectus. Read them carefully before investing.
4. Earn Up to $50 this Month By Answering Survey Questions About the News — It’s Anonymous
The news is a heated subject these days. It’s hard not to have an opinion on it.
Good news: A website called YouGov will pay you up to $50 or more this month just to answer survey questions about politics, the economy, and other hot news topics.
Plus, it’s totally anonymous, so no one will judge you for that hot take.
When you take a quick survey (some are less than three minutes), you’ll earn points you can exchange for up to $50 in cash or gift cards to places like Walmart and Amazon. Plus, Penny Hoarder readers will get an extra 500 points for registering and another 1,000 points after completing their first survey.
It takes just a few minutes to sign up and take your first survey, and you’ll receive your points immediately.
5. This Online Bank Account Pays 10x More Interest Than Your Traditional Bank
If you bank at a traditional brick-and-mortar bank, your money probably isn’t growing much (c’mon, 0.40% is basically nothing).1
But there’s good news: With SoFi Checking and Savings (member FDIC), you stand to gain up to a hefty 3.80% APY on savings when you set up a direct deposit or have $5,000 or more in Qualifying Deposits and 0.50% APY on checking balances2 — savings APY is 10 times more than the national average.1
Right now, a direct deposit of at least $1K not only sets you up for higher returns but also brings you closer to earning up to a $300 welcome bonus (terms apply).3
You can easily deposit checks via your phone’s camera, transfer funds, and get customer service via chat or phone call. There are no account fees, no monthly fees and no overdraft fees.* And your money is FDIC insured (up to $3M of additional FDIC insurance through the SoFi Insured Deposit Program).4
It’s quick and easy to open an account with SoFi Checking and Savings (member FDIC) and watch your money grow faster than ever.
Read Disclaimer
5. Stop Paying Your Credit Card Company
If you have credit card debt, you know. The anxiety, the interest rates, the fear you’re never going to escape… but a website called AmONE wants to help.
If you owe your credit card companies $100,000 or less, AmONE will match you with a low-interest loan you can use to pay off every single one of your balances.
The benefit? You’ll be left with one bill to pay each month. And because personal loans have lower interest rates (AmONE rates start at 6.40% APR), you’ll get out of debt that much faster.
It takes less than a minute and just 10 questions to see what loans you qualify for.
6. Earn Up to $225 This Month Playing Games on Your Phone
Ever wish you could get paid just for messing around with your phone? Guess what? You totally can.
Swagbucks will pay you up to $225 a month just for installing and playing games on your phone. That’s it. Just download the app, pick the games you like, and get to playing. Don’t worry; they’ll give you plenty of games to choose from every day so you won’t get bored, and the more you play, the more you can earn.
This might sound too good to be true, but it’s already paid its users more than $429 million. You won’t get rich playing games on Swagbucks, but you could earn enough for a few grocery trips or pay a few bills every month. Not too shabby, right?
Ready to get paid while you play? Download and install the Swagbucks app today, and see how much you can earn!
As most of these answers covered there are a number of different ways to do this. For icons you're probably best using a sprite for speed and having media queries, and for backgrounds you should do the same. For normal images in most cases I'd suggest not getting too fancy at this point.
In the real world it often doesn't make sense to try and force everything into a media query or have some javascript or backend replacement technique. If you want to set it up and can make it work for your project that's great, but often I find that I'm just trying to get a small to medium size site out for a c
As most of these answers covered there are a number of different ways to do this. For icons you're probably best using a sprite for speed and having media queries, and for backgrounds you should do the same. For normal images in most cases I'd suggest not getting too fancy at this point.
In the real world it often doesn't make sense to try and force everything into a media query or have some javascript or backend replacement technique. If you want to set it up and can make it work for your project that's great, but often I find that I'm just trying to get a small to medium size site out for a client.
Until there is a solution in the HTML spec for replacing images, it makes sense (as Daan Jobsis found: http://www.netvlies.nl/blog/design-interactie/retina-revolution) to just save your image at double the pixel size, compress it to something like 40% and set the width and height in HTML to be half the size of your image file. For example a 400x400px jpg would be <img src="yourimage.jpg" width="200" height="200">.
The image will end up about the same file size as your non-Retina image would have been, but it still has the extra pixels to look nice on the hi-density display.
Where you'll need to start considering the replacement techniques is when you're working with a CMS and clients are uploading images. If you don't have a way to control the compression you'll want to look into a code solution to keep the site speedy (media queries, JS, PHP, etc).
Also I've got an article on this with some of the basics for how to setup the javascript replacement, and some good discussion in the comments here: Creating Retina Images for Your Website
You may want to check out the solution Shaun Inman came up with recently that uses tiny snip of JS to set a cookie and mod_rewrite:
"Automatic Conditional Retina Images"
http://shauninman.com/tmp/retina/
You could target the retina display using CSS3 media queries. See here: http://aralbalkan.com/3331
Or you can target your images directly using jQuery with the retina display plugin: http://troymcilvena.com/post/998277515/jquery-retina
Everyone else seemed to mention going the route of media queries, but personally one of my favorites is possibly the best solution.
Take advantage of the new Picture element, while using a polyfill to add backward support for browsers that don't support the new picture element.
https://www.smashingmagazine.com/2014/05/responsive-images-done-right-guide-picture-srcset/
I saw a technique where you save this information to a cookie and then the server-side script would be able to serve the correct image.
The problem with this is: it requires a reload to work
We used it for a product, and it really worked.
I personally like the browser side approach better.
http://www.bdoran.co.uk/2010/07/19/detecting-the-iphone4-and-resolution-with-javascript-or-php/
There is no real "best method" for doing this. It will probably be a mixture of both CSS and JS to achieve desired results. Here is some plain javascript to replace 1x images in a DOM element with the _2x extension (uses forEach which was implemented in JavaScript 1.6 - ECMAScript 5th edition ). https://gist.github.com/2130072
I have created a script that only downloads one image, supports css background images and images dynamically added with JavaScript. Check out http://retina-images.complexcompulsions.com
The best route I know of is to detect the user agent as being a retina capable device and then sending a response with image URLs which are 2x bigger than needed, but setting the width / height of the image tag to be the normal (rather than 2x'd) size. Same applies for sprites too (but there you can use CSS media queries rather than UA detection). If UA detection isn't your thing, then you will need to do the work client side to replace the low res images with higher res ones. Of course you could also always send the higher resolution images, but then you are wasting bandwidth and making a slo
The best route I know of is to detect the user agent as being a retina capable device and then sending a response with image URLs which are 2x bigger than needed, but setting the width / height of the image tag to be the normal (rather than 2x'd) size. Same applies for sprites too (but there you can use CSS media queries rather than UA detection). If UA detection isn't your thing, then you will need to do the work client side to replace the low res images with higher res ones. Of course you could also always send the higher resolution images, but then you are wasting bandwidth and making a slower user experience for those not using retina devices.
I do like the idea of using javascript to load the proper asset by leveraging the css media query, and a test element, to understand the proper resolution to display.
As proposed in this article by Jake Archibald http://24ways.org/2011/adaptive-images-for-responsive-designs-again
Use retina.js. It will automatically handle swapping out the images for the @2x,@3x, etc versions of the images. This is better than relying on the browser to downscale the image and also keeps the browsers from downloading larger images than needed.
For icons you can use SVGs and have it fallback to pngs:
<img src="icon.svg" onerror="this.src='icon.png'; this.onerror=null;">
I just wrote a jQuery plugin to help with this. You can append a suffix to the existing image, or it can pull from the data-retina attribute on the img tag.
https://github.com/tylercraft/jQuery-Retina
The best method to use images appropriate for each device is to implement SASS or media queries depending on the technologies used to create the webpage.
Media queries are your best friend!
http://blog.iwalt.com/2010/06/targeting-the-iphone-4-retina-display-with-css3-media-queries.html
Wouldn't it be better to use resolution media query to distinguish retina displays by DPI instead of webkit specific query
- -webkit-device-pixel-rat
- io: 1
? I mean something like
- @media only screen and (min-resolution: 200dpi){
- .image{ ... }
- }
. I hate browser specific css/whatever :) What do you think ?
I would shy away from using sprites and use as few pixel-based images as possible. If they are icons, use svg format via a service like icomoon. Only add pixel images when absolutely necessary.
LOL … most front end developers who weren’t lazy, back in the days of HTTP/1.1
Sprites did their work when you had lots of small images(icons) and you wanted to avoid having the browser spawn and queue lots of HTTP requests for them. Every HTTP request/response comes with overhead. There is a headers overhead that multiplies for each request, an overhead in time spent connecting(TCP/IP, Web Server and the rest of the suite of protocols/software that needs to do work along the way). All of that overhead gets multiplied with the number of HTTP requests because HTTP/1.1 is rather stupid. It cannot
LOL … most front end developers who weren’t lazy, back in the days of HTTP/1.1
Sprites did their work when you had lots of small images(icons) and you wanted to avoid having the browser spawn and queue lots of HTTP requests for them. Every HTTP request/response comes with overhead. There is a headers overhead that multiplies for each request, an overhead in time spent connecting(TCP/IP, Web Server and the rest of the suite of protocols/software that needs to do work along the way). All of that overhead gets multiplied with the number of HTTP requests because HTTP/1.1 is rather stupid. It cannot request multiplexing over one TCP/IP connection, it doesn’t compress the overhead all that well, it uses text as opposed to the binary protocol of HTTP/2, it cannot push certain resources(like essential stylesheets/scripts) so that the browser has everything it needs to efficiently start working towards First Meaningful Paint.
We could spend all day talking about JUST HOW MUCH HTTP SUCKS, but these are the tools we work with and sprites were essential in minimizing the suckiness of HTTP/1.1 when dealing with lots of small images.
Great question! There are two considerations when optimizing for iPad and other tablet devices. The first is user experience, and the second is performance. You'll need both to meet your website goals.
User experience
With tablet optimization you can look at addressing core site deficiences that make a site difficult or unusable on tablet devices. Many sites don't need to go any further than this -- they just need a few tweaks.
The alternative approach for optimization is an immersive tablet experience. Taking an immersive approach showcases your website and brand in a unique way and set
Great question! There are two considerations when optimizing for iPad and other tablet devices. The first is user experience, and the second is performance. You'll need both to meet your website goals.
User experience
With tablet optimization you can look at addressing core site deficiences that make a site difficult or unusable on tablet devices. Many sites don't need to go any further than this -- they just need a few tweaks.
The alternative approach for optimization is an immersive tablet experience. Taking an immersive approach showcases your website and brand in a unique way and sets your website apart from other websites that tablet visitors see in their day-to-day browsing. A well designed immersive experience will pay off in increased visits, increased goal conversions and a decreased bounce rate.
Here are some specific user experience optimizations:
Think about how a tablet is used
Consider how your visitor is holding the tablet. The most ccessible touch target areas of your site are in the bottom left and bottom right corners reachable by the users thumbs when the device is held in two hands. Interactions near the top of the screen require a visitor to hold the device in one hand, reach and touch. This doesn't mean you shouldn't put targets outside the reachable thumb regions, but it is something to keep in mind. Immersive tablet experiences will take advantage of these ideal touch regions.
Eliminate horizontal scrolling
You may not have designed your website with a 960px grid system in mind. This will result in a viewport being used that is larger than the pixel widthe of the device, called a horizontal overflow. This can be OK but is not optimal. How big an impact this has on your site depends on how much scrolling is required and what information has been pushed off screen. For an immersive experience you should lay out text in a way that will not require any pinch/horizontal pan/zoom actions from the user and eliminates horizontal scrolling.
Minimize vertical scrolling
Vertical scrolling should be minimized. Immersive experiences will have judicious use of accordion elements to hide less visited functionality on complex pages. Remember that hiding information or building deep information hierarchies is something to be done with caution. It can help or hinder depending on how well it's thought through.
Test portrait & landscape layouts
Your visitor may be holding the device in either portrait or landscape orientation. Never force visitors to hold it one way or the other to visit your site! Immersive experiences may offer functionality suited to one orientation or the other.
Document text
In many cases you'll want your text to be in a slightly larger font than on the desktop site. You don't want your users squinting on a 7" tablet and preferably they should not need to zoom. An immersive experience may include a widget that saves a persistent cookie to allow visitors to adjust font size without zooming as this gives you control over the user experience, what is on screen and off screen, and allows returning visitors see the site with their configured preferences.
Enlarge touch targets including links and input fields (radio buttons, checkboxes, regular buttons and other interactive elements)
These should be easy for the user to touch, and hard for users to accidentally touch on the wrong thing.
Keep your links from being too close together. Ideally, farther than a thumbs width apart. An immersive experience will exhaustively curate how links are distributed.
Key layout issues
Some sites have overlapping elements and other layout issues on tablets. These needs to be handled on a case-by-case basis.
Incorrectly positioned elements, usually due to wrapping. May be caused by increased font size for tablet.
An immersive experience will also revisit the information architecture of the site, taking into consideration the use cases of a typical tablet user as it relates to the purpose of the website. The one web philosophy is to make all content available across all platforms, but there are always tradeoffs and a great website will make it easiest to do the most common activities.
Position fixed elements
Position fixed elements may not work as designed on desktop. Requires testing and a good understanding of target devices preferably guided by analytics and predictions in internet trends.
Fix fly-out and hover based contextual menus
Fly out menus with a lot of items are brittle and often tricky to use even on desktop, especially if they use the hover event.
Remember that there is no such thing as a hover event on touch screen devices. This impacts the navigation structure of many websites. Your menus need to be changed to respond to a touch event.
You should enlarge the touch targets on your menus.
An immersive experience will consider available tablet screen real-estate to make sure presented menu items fit inside of the page and do not require vertical or horizontal scrolling to access.
Touch gesture functionality
Immersive sites will introduce touch gesture functionality. The most commonly used is swipe for image carousels. Additional behaviours that can be introduced include touch-drag, multi-touches (targetTouches) where the user has multiple fingers on the display.
Sensor functionality
HTML5 has given us access to a variety of sensor data including location, device shake, acceleration, rotation etc. Availability of sensor functionality varies by operating system and device. Using this functionality is often a component of an immersive site.
Images
Detect high definition (HD) displays and serve high quality images where appropriate. Low quality images will lower the perceived quality of a website on devices with HD displays. Immersive sites will have high quality images throughout the experience.
Performance
Wi-fi tablets are more popular than 3G models. This doesn't mean you're out of the woods on performance! Keep in mind tablet visitors may not be at home or close to their wi-fi access points. Your visitor may be at a hotel, resort, coffee shop, on an airplane, or in their back yard at the edge of their wi-fi range. In any of these cases they may have less than ideal bandwidth. The computational (CPU) power available to tablets is also substantially less than on desktop. A slow website will convert poorly and leave visitors with a bad impression. This is especially true on tablets which are often used during limited time intervals ("I have five minutes to wait for my train, I'll surf the web on my tablet").
Immersive experiences will be carefully tuned to provide the optimum balance between rich functionality and performance. Keep your pages as small as possible. Implement performance best practices such as minimizing number of resource requests, scripts, images. Minify your CSS & JavaScript. Only include what is absolutely necessary. Cloud script optimization services can do this for you in an automated way. Remember that the browser pre-fetch thread on responsive sites will fetch even resources that are hidden on most tablet browsers today including the iPad. Use intelligent image optimization services that provide images at a resolution appropriate for the display resultution (HD or SD) and compressed for the connection speed of the visitor.
Remember your visitors are on a device that uses batteries. Immersive sites will be kind to a visitor's battery life and minimize running scripts to those absolutely needed and avoid poor coding practices such as busy waiting.
The HTML-5 Canvas does. In HTML it is all Images and or CSS images which they are all Sprites. Gif Images allow movement within their Pixel Positions as Sprites. And JavaScript can move HTML Images also but not the preferred way to do it but rather by switching images as gif to work as moving backgrounds in Text, Banner text and behind text etc. You will Want GIMP. Search it and learn about Transparent Images and gif creation.
While this is a nice approach, to scale nicely on ANY environment you may want to consider ditching the "Retina Tax" of downloading multiple images (especially for mobile), and create your own icon font file set. The process would go like this:
- Create a vectorized version of an icon you want to use
- Export icon as SVG
- Import to a typeface creator, or a service such as IcoMoon and generate the necessary font files (.woff, .ttf, .eot, etc.)
- Craft typeface definitions in your favorite preprocessor language or straight CSS
- Create your icon glyphs classes using the :before pseudo class and the content a
While this is a nice approach, to scale nicely on ANY environment you may want to consider ditching the "Retina Tax" of downloading multiple images (especially for mobile), and create your own icon font file set. The process would go like this:
- Create a vectorized version of an icon you want to use
- Export icon as SVG
- Import to a typeface creator, or a service such as IcoMoon and generate the necessary font files (.woff, .ttf, .eot, etc.)
- Craft typeface definitions in your favorite preprocessor language or straight CSS
- Create your icon glyphs classes using the :before pseudo class and the content attribute, matching up the characters assigned previously to the unicode:
- .icon-twitter:before{ content:'\e608'; } //example
- Then use as an element in your DOM:
- <p><em class="icon-twitter"></em> Follow Me on Twitter</p>
It's clever, but simpler than you think.
They use HTML5 videos for all the device animations and attach javascript listeners to monitor video playback time-coding. Depending on the client's window scroll position, the videos are configured to play only up until a certain timestamp that approaches the full duration of the video as the client continues to scroll.
You can inspect this effect in action for yourself by right-clicking on any of the device animations and check Loop. Right-click once more and choose Play.
The rest of the effects are your tried-and-true CSS3 animations firing upon client
It's clever, but simpler than you think.
They use HTML5 videos for all the device animations and attach javascript listeners to monitor video playback time-coding. Depending on the client's window scroll position, the videos are configured to play only up until a certain timestamp that approaches the full duration of the video as the client continues to scroll.
You can inspect this effect in action for yourself by right-clicking on any of the device animations and check Loop. Right-click once more and choose Play.
The rest of the effects are your tried-and-true CSS3 animations firing upon client scroll position.
Well, you could do it that way. It's how early CSS sprites were made. But in the real world you'll either use a tool to handle it for you or a CSS preprocessor like Sass/Compass which will do it all seamlessly. The process is something like:
- Make a folder for all the sprite images
- Use a one-line Compass function in your Sass file to import all the images from that folder
- Continue writing CSS referring to each image by its name rather than its path
- Profit
Taking into account adaptive (or responsive) design principles to ensure the content of the page adjusts to the size of the screen. This is done, typically, with @media queries in your CSS. And, possibly, with viewport parameters in your HTML. Essentially making it so users wont have to pan/zoom in order to take in the content of the page. It's also a good idea to make sure all buttons and navigation items are at least 30x30 pixels (so your finger can hit it without feeling awkward).
Additionally, you can use some of Apple's suggestions when designing web content for mobile https://developer.a
Taking into account adaptive (or responsive) design principles to ensure the content of the page adjusts to the size of the screen. This is done, typically, with @media queries in your CSS. And, possibly, with viewport parameters in your HTML. Essentially making it so users wont have to pan/zoom in order to take in the content of the page. It's also a good idea to make sure all buttons and navigation items are at least 30x30 pixels (so your finger can hit it without feeling awkward).
Additionally, you can use some of Apple's suggestions when designing web content for mobile https://developer.apple.com/library/ios/#DOCUMENTATION/AppleApplications/Reference/SafariWebContent/ConfiguringWebApplications/ConfiguringWebApplications.html to utilize Apple Touch Badges (Home Screen icons), start-up images, hiding the Safari UI, etc
What is responsive design?
What is the difference between responsive and adaptive design?
What are some examples of tablet-optimized websites?
There are a few ways to solve this...
1. Stack icons in the sprite in a diagonal fashion
This approach is not good for the PNG file size, but it can help with overflowing heights on the elements you're pinning the sprite to.
See: http://www.aaronbarker.net/2010/07/diagonal-sprites/
2. Apply the sprite to small inline-block elements
In this example:
- <h3>News</h3>
You could add an empty span in front of the word you're using, to act as the target area for your icon.
- <h3><span class="icon icon_news"></span>News</h3>
It's not great for semantics or maintenance, but it is better for performance.
Then
There are a few ways to solve this...
1. Stack icons in the sprite in a diagonal fashion
This approach is not good for the PNG file size, but it can help with overflowing heights on the elements you're pinning the sprite to.
See: http://www.aaronbarker.net/2010/07/diagonal-sprites/
2. Apply the sprite to small inline-block elements
In this example:
- <h3>News</h3>
You could add an empty span in front of the word you're using, to act as the target area for your icon.
- <h3><span class="icon icon_news"></span>News</h3>
It's not great for semantics or maintenance, but it is better for performance.
Then give the <span> inline-block properties and apply the sprite background.
- span.icon {display:inline-block; width:16px; height:16px; margin-right:0.25em; vertical-align:middle; background-image:url("sprite.png"); background-repeat:no-repeat;}
- span.icon_news {background-position:0 -50px;}
3. Add vertical spacing to the sprite image
Instead of making the icons almost touch one another in the sprite you're creating, what I used to do was create enough vertical space between each icon so that you necessarily wouldn't see the next image in the sprite if the element overflowed its ordinary height.
So, at every 50px or 100px in the sprite, draw a guideline and then place the next sprited icon at that position.
This technique has the added benefit of making your CSS more maintenable too, e.g.:
- .icon_news {background-position:0 -50px;}
- .icon_about {background-position:0 -100px;}
- .icon_contact {background-position:0 -150px;}
- /* etc */
BONUS. Consider using data:URI images.
If you don't have to support IE7+8 over SSL and IE7 in general, you could switch to base64 images embedded in a CSS file. (Mirror that in an MTHML file for IE6/7)
data:URIs are much easier to maintain because you don't have to create a sprite in the first place. A simple commandline operation (in *nix or Mac) can convert the image into base64 text, or you could use one of the many online base64 converters.
No more clumsy background-position setting, and it would correct the issues you're facing with the next image being visible in your sprite.
Oh, and greetings from South Africa :)
This is the high-resolution variant of the Apple screen. The exact resolution depends on the size of the screen. I am typing on my iPad with a retina display, and I work on a 13″ MacBook Pro, also with a Retina screen.
The idea is that the pixels are so tiny that you can no longer see them with the naked eye. So the effect is that text appears like a printed page.
It' very nice.
Sadly, we get spoiled easily. Because I also work about 50% in various Windows machines, I found that I was hating the regular HD (1920x1080) resolution, as it was much lower than what I was accustomed to on my Mac, and i
This is the high-resolution variant of the Apple screen. The exact resolution depends on the size of the screen. I am typing on my iPad with a retina display, and I work on a 13″ MacBook Pro, also with a Retina screen.
The idea is that the pixels are so tiny that you can no longer see them with the naked eye. So the effect is that text appears like a printed page.
It' very nice.
Sadly, we get spoiled easily. Because I also work about 50% in various Windows machines, I found that I was hating the regular HD (1920x1080) resolution, as it was much lower than what I was accustomed to on my Mac, and it made my eyes water. So I had to upgrade my laptops and external screens to 4K resolution, which is comparable to Retina on Apple.
Now I'm happy.
I have a weebly website, and I wouldn’t actually recommend them inspite of their low prices compared to other webbuilders such as photoshelter and squarespace “which are way better btw” for one reason, they don’t support retina displays which means if you’re viewing the website from a retina monitor like a macbook or a 4k display, you’ll view the images pixelated and blurry … I kept looking up the web for the reason; at the beginning I thought it was an image size issue, but turns out they dont support retina displays.
Second, nobody uploads full size images on web, they’re waaaay more you need
I have a weebly website, and I wouldn’t actually recommend them inspite of their low prices compared to other webbuilders such as photoshelter and squarespace “which are way better btw” for one reason, they don’t support retina displays which means if you’re viewing the website from a retina monitor like a macbook or a 4k display, you’ll view the images pixelated and blurry … I kept looking up the web for the reason; at the beginning I thought it was an image size issue, but turns out they dont support retina displays.
Second, nobody uploads full size images on web, they’re waaaay more you need to display on any website, weebly shrinks background and gallery images to 1100 pixels for the longest edge no matter how big your image is, so before uploading images make sure you optimize them well for web, there’s a lot of photoshop actions to handle this for you, but again “Weebly is not a good idea” .
Retina Display is an Apple marketing term. It means that the pixel density is so tight, then when viewed from a typical viewing distance, the individual dots (pixels) are imperceptible to the human eye. The purpose of Retina Display technology is to make curves and angled lines appear to be smooth lines. Without Retina Display technology, iPhones had a jaggie look on certain angles, because the pixels are oriented in a square grid pattern. By making the dots so small and close together, that you cannot see them, you can make angled lines, and curves appear to be flawless.
Take a look at this ar
Retina Display is an Apple marketing term. It means that the pixel density is so tight, then when viewed from a typical viewing distance, the individual dots (pixels) are imperceptible to the human eye. The purpose of Retina Display technology is to make curves and angled lines appear to be smooth lines. Without Retina Display technology, iPhones had a jaggie look on certain angles, because the pixels are oriented in a square grid pattern. By making the dots so small and close together, that you cannot see them, you can make angled lines, and curves appear to be flawless.
Take a look at this article. There is a visual example.
Retina Display: Is It Worth It?
Update: The first iPhone to offer a retina display was the iPhone 4, released on June 24, 2010, with a pixel density of 326ppi. The next jump was the iPhone 6plus (and other plus models) with a pixel density of 401ppi. The iPhone X (Apple’s first OLED phone) has a pixel density of 458ppi.
I consider myself an experienced web developer on the cutting edge and was completely unaware of the concept of "retina ready" until a customer told me his images looked blurry on a photography website I built for him about a year ago. I was aware retina displays existed, but I never really thought of how they worked or that you had to do special tricks to get them to render websites in retina resolutions. I told him I sized them the exact size they were displayed on the browser and they looked great to me... he wasn't buying it. I tried several different resizing algorithms and still he co
I consider myself an experienced web developer on the cutting edge and was completely unaware of the concept of "retina ready" until a customer told me his images looked blurry on a photography website I built for him about a year ago. I was aware retina displays existed, but I never really thought of how they worked or that you had to do special tricks to get them to render websites in retina resolutions. I told him I sized them the exact size they were displayed on the browser and they looked great to me... he wasn't buying it. I tried several different resizing algorithms and still he complained of the quality. Fucking perfectionist I thought... I finally got on a screen sharing session with him and had him show me the problem, there I discovered he was on a mac and you could notice a difference. I was on a cinema display and still couldn't figure it out. After using developer tools to look into it more I was finally able to see the browser zooming going on.
If you were a developer with a retina display, of course you would know about the quality retina brings, but if you don't have access to one, anything outside of that, you have to jump through hoops just to simulate it by zooming the browser and its really subtle.
So to answer your question, there are a few reasons:
- Any developer not on a retina display, particularly on windows is likely not going to be aware there is better than actual resolution.
- How retina scaling works is very abstract. The browser still reports it's at the native resolution that's have the resolution it's capable of rendering at. Its not like a new feature that breaks functionality or exposes a new property or something that would tell you there is new capability. Everything works just as well as it use to on non-retina sites.
- Most customers will not ask for it and are just as unaware it exists. Even those on retina displays may not be aware that you have to code differently to take advantage of it. Retina users make up < 10% of the market. You will likely get more penetration by supporting IE8 vs supporting retina. Not supporting retina also doesn't greatly degrade the experience for retina users... its very subtle and likely won't be noticed unless you're site's core value proposition is in image quality.
- Supporting it means you have to make multiple images or force users on non-retina display to quadruple the size the image they have to download.
- Additional coding for it is trivial on new projects, but much more difficult on existing code depending on how things were implemented. In all cases, it is more work though. Tools are getting better though and more retina displays are coming, but its going to take much longer then most other new technologies to be adopted, I wouldn't be surprised if its another 5 to 10 years before the majority of big name sites have great support for retina displays.
javascript gaming with sprites and canvas.
The is a channel called Frank’s Laboratory which has a lot of videos and compete courses on the topic..
It’s much simpler than you’d expect.
Basically you have images that have their position set to absolute.
You’ll need to specify the default X Y coordinates for their initial placement.
Next you’ll need to write a snippet of JavaScript to detect the window’s scroll event.
Within the scroll event, you’ll write a function that dynamically modifies the X or Y coordinates. (Apple uses the transform property because of its performance advantages vs top/bottom properties)
To ensure you’re not wasting resources, ensure that the scroll event detects whether or not your target images are visible within the v
It’s much simpler than you’d expect.
Basically you have images that have their position set to absolute.
You’ll need to specify the default X Y coordinates for their initial placement.
Next you’ll need to write a snippet of JavaScript to detect the window’s scroll event.
Within the scroll event, you’ll write a function that dynamically modifies the X or Y coordinates. (Apple uses the transform property because of its performance advantages vs top/bottom properties)
To ensure you’re not wasting resources, ensure that the scroll event detects whether or not your target images are visible within the viewport at any given time.
This eliminates unnecessary processing of images that are not currently visible by the user.
Here’s a video to give you a hint of what I’m referring to: Screen Capture on 05-25-2016.mp4
Good luck!
There are a lot of options, for example:
- Affinity Designer
- Adobe Illustrator
- Sketch
I’d suggest trying all three to see which one works best for you.
If you look around, you will find a number of preprepared icon grids/templates on the internet that you can use to simplify your workflow when it comes to exporting icons in a range of sizes.
You will find templates for pages like these under the category "product landing page". The fact that it has full screen images doesn't really put it in a new category. Although I might say: responsive product landing page.
Since respnsive pages are made to adapt to the small screen of a mobile phone, a lot of them (most?) have edge to edge images with no margin.
I hate quickly writing an answer without being able to put much thought into it, but I am very busy today and wanted to leave this link for you to look over. I believe it will be helpful.
https://medium.com/@dhg/82ced812e61c
I'm only an iOS app dev, so I don't really know what conventions there are but in my opinion, you should provide a PNG file for every dimension that it will be shown.
You should not scale up because then the user is going to see blocks / blurs.
However, you definitely don't want to scale down either, because this makes your sprites look blurred (50% * 1px creates a 50-50 alpha blend).
There are loads of games that do scale their resources, and you either end up with a blurry design or a pixel-y design and it looks terrible.
So as soon as you create some zoom-in effect or something, provide the app
I'm only an iOS app dev, so I don't really know what conventions there are but in my opinion, you should provide a PNG file for every dimension that it will be shown.
You should not scale up because then the user is going to see blocks / blurs.
However, you definitely don't want to scale down either, because this makes your sprites look blurred (50% * 1px creates a 50-50 alpha blend).
There are loads of games that do scale their resources, and you either end up with a blurry design or a pixel-y design and it looks terrible.
So as soon as you create some zoom-in effect or something, provide the appropriate additional sizes as well.
In a decidedly marketing perspective, it's a collective term that describes greater screen pixel density (resolution), higher contrast ratio between blacks and whites, and usage of In-plane Switching (IPS) technology.
However, in realizing this implementation, Apple also built a patented system for mitigating image edge discoloration. The system also prevents unwanted artifacts due to electrical coupling (a.k.a. cross-talk), which occurs due to the adjacency of LCD subpixel columns. You can view the patent from this link: http://1.usa.gov/MHjbYp.
More informed reading at: http://www.patentlyappl
In a decidedly marketing perspective, it's a collective term that describes greater screen pixel density (resolution), higher contrast ratio between blacks and whites, and usage of In-plane Switching (IPS) technology.
However, in realizing this implementation, Apple also built a patented system for mitigating image edge discoloration. The system also prevents unwanted artifacts due to electrical coupling (a.k.a. cross-talk), which occurs due to the adjacency of LCD subpixel columns. You can view the patent from this link: http://1.usa.gov/MHjbYp.
More informed reading at: http://www.patentlyapple.com/patently-apple/2012/06/apples-retina-display-patent-comes-to-light.html