Navigation is so-so. Don't see and decent search options yet. Performance is OK but they don't have much traffic yet. Layout is nice, but just pretty isn't near enough to displace BP or the others. Needs too much scrolling on iPad, probably too much real estate on a monitor too. We shall see. Ladies won't go there if guys don't contact them from there.
Smart to get providers to sign up first, but who knows if they will have a workable marketing plan beyond that. Just my 2cents.
Originally Posted by austxjr
As I have mentioned... I have had a very extensive conversation with LeeAnn the owner of Slixa. I generally go in with a list of questions because I know what my advertisers are looking for.
In Reference to the mobile version of the site. I asked her about that when we spoke and they are the beta stages of what is known as RWD
Responsive Webdesign. Only about 3% of the webdesign on the web now is RWD and this is very progressive thinking for a company. So very soon any concerns about mobile applications will be solved. It seems this company intends to be the leader in this industry and revolutionize the hobbyost and provider's experience.
As for a marketing plan I can tell you there has never been a launch with this much clout behind it. Here's how Lee Ann Explained it to me in a follow up email:
Staff Edit: Contents of email removed per rule #9 of the guidelines. CZ.
Here's a little about RWD.... It will probably boar most but it might actually give some you techies wood...lol
Responsive web design
From Wikipedia, the free encyclopedia
Jump to:
navigation,
search
An example of a responsive website,
The Boston Globe, displayed on multiple devices
Responsive web design (often abbreviated to
RWD) is an approach to web design in which a site is crafted to provide an optimal viewing experience—easy reading and navigation with a minimum of resizing, panning, and scrolling—across a wide range of devices (from desktop computer monitors to mobile phones).
[1][2][3]
Elements of responsive web design (RWD)
A site designed with RWD
[1][4] uses
CSS3 media queries,
[3][5][6] an extension of the @media rule,
[7] to adapt the layout to the viewing environment—along with fluid proportion-based grids
[8] and flexible images:.
[9][10][11][12]
- Media queries allow the page to use different CSS style rules based on characteristics of the device the site is being displayed on, most commonly the width of the browser.
- The fluid grid concept calls for page element sizing to be in relative units like percentages or EMs, rather than absolute units like pixels or points.[8]
- Flexible images are also sized in relative units (up to 100%), so as to prevent them from displaying outside their containing element.[9]
Related concepts
Mobile first, unobtrusive JavaScript, and progressive enhancement
"Mobile First" and "
Unobtrusive JavaScript"/"
Progressive Enhancement" (strategies for when a new site design is being considered) are related concepts that predated RWD: browsers of basic mobile phones do not understand Javascript or media queries, so the recommended practice is to create a basic web site then enhance it for smart phones and PCs—rather than try "graceful degradation" to make a complex, image-heavy site work on the most basic mobile phones.
[13][14][15][16]
Progressive enhancement based on browser-, device-, or feature-detection
Where a web site must support basic mobile devices that lack Javascript,
Browser ("user agent") detection (also called "
browser sniffing"), and
mobile device detection[14][17] are two ways of deducing if certain HTML and CSS features are supported (as a basis for progressive enhancement)—however, these methods are not completely reliable.
For more capable mobile phones and PCs,
JavaScript frameworks like
Modernizr,
jQuery, and
jQuery Mobile that can directly test browser support for HTML/CSS features (or identify the device or user agent) are popular.
Polyfills can be used to add support for features—e.g. to support media queries (required for RWD), and enhance HTML5 support, on Internet Explorer. Feature detection also might not be completely reliable with older browsers: some may report that a feature is available, when it is either missing or so poorly implemented that it is effectively nonfunctional.
[18][19]
Challenges, and other approaches
Luke Wroblewski has summarized some of the RWD and mobile design challenges, and created a catalog of multi-device layout patterns.
[20][21][22] He suggests that, compared with a simple RWD approach, Device Experience or RESS (Responsive Web Design with Server Side Components) approaches can provide a user experience that is better optimized for mobile devices.
[23][24][25] Server-side "
dynamic CSS" implementation of stylesheet languages like
Sass can be part of such an approach.
One problem for RWD is that
banner advertisements and videos are not fluid.
[26] However
search advertising and (banner)
display advertising support specific device platform targeting and different advertisement size formats for desktop, smartphone, and basic mobile devices. Different
landing page URLs can be used for different platforms,
[27] or
AJAX can be used to display different ad variants on a page.
[21][28][17]