Showing posts with label website building. Show all posts
Showing posts with label website building. Show all posts

Thursday, October 24, 2013

Need Some Direction to Improve Your Responsive Web Design?

                                               bradfurdfrostweb.com

Knowing how responsive web design can be frustrating at times we have provided some tips from sources that will help you in your endeavors.


1. Why use Responsive Web Design?

RWD is a cheap option; you can re-purpose your existing desktop layout to ensure it works well on a smaller mobile device. If you’re developing a new site, there are few reasons not to use RWD.

However, are you considering RWD because it’s an inexpensive way to tick a few business strategy objectives? You can certainly implement a mobile layout within a few hours but will it be useful? It’s usually obvious when a responsive design has been added as an afterthought. It may be better to stick with a good desktop layout than undermine your online presence.

2. Consider the Context, but…

…avoid stereotypes.

Historically, designers considered desktop viewers to be static and smartphone users to be roaming. A train company would typically highlight ticket buying on desktop devices and station directions on mobile devices. There are a couple of problems with this approach:
the boundaries have become blurred. People use whatever device is practical e.g. they may surf the net on a phone while watching TV.
RWD reveals nothing about the context. Device resolution is a crude assumption especially when you consider the high-density displays offered by modern phones and tablets.

If static and roaming users have different contexts, it may be preferable to provide separate mobile sites or apps which have dedicated functions.

3. Distill Your Content

Why do people visit your site? What’s important to those users? What’s their typical journey? Without these answers, you’ll be tempted to throw everything on the home page. That may be possible on a large display but you’ll struggle when switching to a mobile layout.

The best option: think small-screen first, then
…
4. Design Upwards

Once you have a design for the smallest practical screen, you can work upwards in a series of media query breakpoints.

While there are no strict rules, breakpoint steps should not be large — perhaps no more than 200 pixels. However, each step need not be a major re-flow such as additional columns; it could be a font-size change, floating images or another simple tweak.

5. Keep it Fluid

Ideally, your design should be fluid between breakpoints — not fixed. While fixed layouts are easier to comprehend and code, they’re too fragile for RWD (refer to Is Your Responsive Web Design too Fragile?)

Ideally, even your media queries should use proportional units such as %, em and rem instead of pixels.

6. Never Compromise

RWD should never be used to offer a watered-down version of your website. In some cases, you should consider additional facilities on mobile devices such as geo-location and off-line support. Keep it simple and easy to use:
don’t use browser sniffing
don’t disable zooming
don’t hide content.
7. Only Performance Matters

RWD may be cheap to implement but it should be planned from the start. Applying RWD to a site serving 1Mb+ pages will never result in an optimal experience on devices operating over a mobile network.

Considerations In Building a DIY Website Builders for Responsive Design



1) Some hosting facilities offer DIY building software and even offer free domain name registration. Be careful when taking on this sort of package. Find out who controls the domain name. Is it the client or the hosting facility? It can be difficult to secure or move the domain name if the facility owns or controls the domain name.

2) DIY builders are low cost – but are sometimes limited in terms of layout, graphics along with limited features and functionality. What initially seems like a good idea can end up being a frustrating experience.

3) When using a DIY site builder – the software will build an interface and internal web pages from some available templates, which is not always a bad thing. But the designs are usually considered "proprietary", and more often than not, they are tied into the back-end database which is owned by the facility. Then it can be difficult, if not impossible to move a site if desired.

4) Updating ones site can be a rewarding experience. It can also be a time-consuming exercise. It's best to first ask the question; how much time does the website maintenance take and could the time be better spent on building the business instead.

5) Usually the overall design can be “acceptable”. But is “acceptable” good enough? Remember, it’s the company’s “brand” that is at stake and one never gets a second chance at a good first impression.

So, there are many things to consider when building the company website including the design, layout, ease of moving a site if necessary, scalability and much, much more. More often than not, it's better to out-source the development to experienced developers and end up with a better business website. Consider talking to a local web design company in the area to answer any questions that might be important when making that decision.

IFM Web Services offers Responsive Web Design, website analysis, SEO Press releases, Search Optimization and Facebook pages for businesses. Located in the Toronto area (GTA), IFM has helped business achieve an effective online presence and has helped clients as far away as Bermuda and Mexico. For more on Social Media, SEO or Web Design for businesses, visit IFM at http://www.ifm.ca

http://www.sitepoint.com/7-responsive-web-design-tips/

http://www.prweb.com/releases/2013/10/prweb11255072.htm

Wednesday, October 23, 2013

Why is it Important to Know If Your Website Was Built in Open or Closed Source Code

Realizing that most website owners are just happy that their site is functioning well and looks great. Have these businesses ever realized that they need to educate themselves about the technology on the back side of their website?

Craig Reardon has some great advice to give on the subject.

There are three really important questions smaller business operators need to know about their website technology: Who recommended the website technology you are currently using? How impartial was that recommendation? And why is it important anyway?

The answers to these lie in a debate the software industry has been battling out for decades now. That of ‘open’ versus ‘closed’ source development code.

Before you click over to something a little more interesting than computer code, it’s important that you read on. Because not knowing the difference can greatly impact your expenses, your sales and even your reputation.

The open source community method

By definition, ‘open’ source means that software and now web developers are able to access the computer programming of the software or website in question and alter it to create new functionality.




The closed proprietary alternative
On the other hand, ‘closed’ source software or technology does not allow ordinary developers to access the development source code in this way. Typically companies create such software and deliberately ‘close’ the source code so that only they can modify it.

This is not just for purely profit motives. Closing the code in this way allows you to control the quality of the software by preventing ‘enthusiasts’ from inadvertently creating faulty or insecure programming code, which of course can compromise the software brand and reputation.

As a result, any issue you have with the software is generally directed back to the company who provided it, sometimes via licensed local developers. As in any manufactured product, warranties and service level agreements cover any fault that might occur to your program.

Packaged, branded technology

The best analogy to this community versus company scenario lies in your standard book-keeping programs. In the very early days of personal computing, you could hire a programmer to develop or ‘write’ a book-keeping program for you. Because ‘off the shelf’ book-keeping systems were still new (and we are talking 25 years ago or more) your only real option was to pay the hourly rate for a programmer or developer to create it for you.

But because computer code can easily be duplicated in much the same way music now can, it made sense for the developer in question to make the software available to others for a price much lower than having to re-create it each time.

So very quickly entrepreneurial developers packaged up their programs and mass produced and marketed them, much like MYOB, Quicken, etc do today.

Whilst you pay an initial and usually ongoing license fee to purchase and use closed software, you also get teams of trained professionals ensuring its upkeep and quality control – particularly in an industry renowned for disgruntled or otherwise meddlesome hackers constantly trying to create havoc.



Famously, this battle of Open vs Closed was fought out between Microsoft and Apple when it came to the way they licensed their operating systems and software. Microsoft’s ‘open’ approach allowed pretty much anyone with any development nous to incorporate its operating system into its hardware, regardless of its quality, and in so doing allowing the market for it to flourish. And it’s the reason why it held up to 94% of the operating system market at one point.

The core of Apple

On the other hand, for all but a few years Apple completely closed its operating system to outside providers so as to control the complete product in much the same way that many car manufacturers do. Whilst this approach came very close to ensuring its demise at one point, it eventually led to hugely successful vertical integration possibilities as is now being realised by its hardware, operating system, iTunes, app store, etc, products.

Actually, Apple may not have happened at all if co-founder Steve Wozniak had his way. He wanted the original Apple 1 to recoup only the cost of the hardware, add a small profit margin and essentially give away the operating system before Steve Jobs talked him out of it – a decision that took the fledgling business out of the hobbyist market into the consumer market, with revolutionary results.

But coming back to website technology, business operators can now choose from an open source website platform or a closed proprietary one – something that few actually realise or are even alerted to by their web professional.

The cost of freedom

But whilst an open approach may provide developers with all the freedom they need to be able to create pretty much any kind of website, it also creates the potential for a number of problems that closed systems don’t.

These relate to quality, upgrades, maintenance, security, other improvements and the cost of each of these.

But whilst an open approach may provide developers with all the freedom they need to be able to create pretty much any kind of website, it also creates the potential for a number of problems that closed systems don’t.
These relate to quality, upgrades, maintenance, security, other improvements and the cost of each of these.

Unlike a license with a closed or proprietary provider, there is no obligation on the part of your web developer to ensure that your website platform is kept up to date with all the various ongoing maintenance requirements web technology require.

So, say browsers such as Internet Explorer or Chrome alter their operational specifications? Your developer must keep up with these (regular) changes and ensure your website meets them; whereas proprietary providers do this regular maintenance as a matter of course – because at some point you have paid for it.

So what has all this background information got to do with you as a smaller business operator? As it now turns out, plenty.

http://www.smartcompany.com.au/technology/34246-is-your-website-built-in-open-or-closed-source-code.html