John Resig + Ars Technica = True

John Resig, Mr jQuery, has his first article out on Ars Technica, it is about Extreme JavaScript Performance, where John discuss performance of JavaScript Engines SquirrelFish Extreme, TraceMonkey and V8.

Interesting to start read John on Ars Technica. He plans on being a regular poster:

I plan on contributing an article per week, or so, on topics related to JavaScript, browsers, and standards. I consider this to be a good challenge for myself – I have to perform considerably more research (interviewing, etc.) than I would for a normal blog post (which isn’t to say that I won’t for my blog – but that this is starting to get me in the good habit of doing additional fact-checking).

 

Long Term vs. Short Term Online Business

I work in an industry where a lot of people try to chase after the big money with small efforts invested, looking for quick cash. Seldom their expectations are met. What brings the cash in is long term dedication towards strict economical, and other measurable, goals. This holds for true with online businesses as well, a lot of people is looking for the big cash-in, either through advertising, affiliation or selling one of its properties. Instead of buying useless “Universal Solutions” for making you a millionaire over night, try to set the correct goals for being a millionaire within 5-10 years instead. Otherwise you will only feel frustrated every single day, when you miss out on your short term goal to become an online millionaire. Of course there will be a YouTube sold to Google every year or so, but I wouldnt put to high expectations on it happening to me. In this article I will think out loud about starting up your own small online business. 

It is not all or nothing

Whenever you end up in a discussion whether or not a solution would fit as an online business and make you money, a lot of people end up saying “That has already been done”, yes of course, but that is not a relly good argument, look at the shelves at your convenient store, there are more than one brand of cereals, right? The good thing with online businesses is that you can choose to target any market you like, even ultra competitive markets can be targeted. With the right online marketing techniques, long term dedication, geographical location and niche you should be able to monetize both short term and long term, but with the possibility to expand geographical location and niche as a long term goal. 

Set up close to realistic goals

Without goals you do not know if your business is running good or bad. You have to have detailed goals; economical, traffic growth, service evolution, budget for online marketing etc etc. It is crucial that you know your market, your future customers and you competitors. By analyzing the competition and competitors offers, you will get better information on how to set up your long term goals. Tools and techniques you can use for evaluation of these things can be:

  • Web services such as Alexa.com and Compete.com
  • Set up comparative analysis tables for 3-5 competitors to see if there is a niche not yet covered/focused on by competitors.
  • Keyword analysis, to find bargain keywords to focus your SEO and PPC efforts on.
  • Check with Commission Junction, TradeDoubler and other Affiliate Networks if you can find affiliate programs that easily can be monetized on your online business.
  • Try to buy adspace on competitors to get an idea of what they are charging for advertising space.

When you have identified the competitors and economic possibilities, try to set a short term goal and a long term goal. The short term goal must in no way compete with the long term goal. My suggestion is to set up goals that are realistic + 20%, that way you are pushing your self. A typical short term goal could be to say “In three months my business must have 5000 Unique Visitors per month” and a long term goal could be to say “Within 3 years my business should generate enough income for me to pay for my car, phone and apartment”. 

Measure and evaluate

Set up different measure points, that will tell you wether or not you are going in the right direction towards your long term goals. These measure points is often called KPI (Key Performance Indicator) and is used to get a health score on your business. What you need to do is to identify things that can be measured and set a value on those kind of things. A typical example could be:

  • A user signup is worth $10
  • A new unique visitor is worth $0.05
  • Conversion rate vistors-to-users, users-to-buyers, buyers-to-returning-buyers etc.

The value of these different actions is of course an equation based on how you convert your users to paying customers, and by tuning conversion rates, values of different actions may increase in value. Of course you can measure “soft values” as well (design, first impression, brand recognition) but for that you need some kind of interaction with the user through interviews or surveys on a regular basis.

Baby steps is better than no steps at all

By taking the scientific approach to your business, you are going in the right direction, and sooner or later you will start seeing result on your daily income from your online business. It can be very frustrating to see that you only make small number of sales and leads early in your business, but the fact that someone is actually doing something making you money, is an evidence that you have something that works for someone. Now you just have to use all your evaluation tools to identify when it works for who. By doing this, you will increase the chances for earning more money, but it can be a time consuming job, that is why long term is the key. Try to identify what works, and tune that, try to identify what do not work and redo that. But remember: What works short term, may not work long term. Adsense ads all over your website may work for unique new visitors, but I bet you see a high bounce rate and low pageviews/visit.

Do not expect wonders

If you have competition on the business you have chosen to focus on, you will have to fight hard to gain market shares and traffic to your business. Sometimes people find a niche where competition is low and traffic is great, but I do not think it happens too often nowadays. Hard long term work will make it work for you, but do not expect short term miracles when applying a long term strategy to your online business. Sooner or later traffic and earnings will explode if you focus hard. There are no easy ways to success (except luck and exceptional timing)

Conclusion

There are no shortcuts to making huge amounts of money online. But you can gain leverage on your competition by setting up long term goals, KPI:s, evaluate daily, weekly, monthly, tune your product, listen to your users and have faith in your business being a success long term. Avoid setting short term goals that may harm your long term product strategy.

Front-End Architecture: The Pre-Study

This article is the first article of 30 in my series on Front-End Architecture. The goal with the articles is to document things I have never documented and share knowledge and experience to anyone that are interested in the architectural decisions made.

Get to know your problem domain

Before starting a big redesign you have to identify, quantify and gather data on almost everything that has anything to do with your front-end architecture. What I would do first is to read the requirement specification and business goals for the redesign of the web you are working on. I have seen a lot of requirement specifications and to be honest, I have yet to see a requirement specification that puts front-end requirements clearly. If the requirement specification fails to specify requirements that affect the front-end architecture, I stress the value of creating a pre-study focusing on all the aspects you may think of. Below I list some of the areas I think is crucial to address in a front-end pre-study.

Statistics

How many daily visitors can you expect? What type of clients can you expect visiting your website, instead of looking at the current statistics, look at trends over a period of at least half a year, this way you are sure you will not miss any significant data hiding in the stats.

Performance

If you are redesigning your website, measure everything you can measure and if you are building from scratch, look at competitors as guideline to what you have to achieve at least. Things I would measure is
• HTTP-requests
• Response times
• Render time
• Download size
There are a lot of online tools you could use for measuring stuff like this. Please visit WebSiteOptimization.com

Design Paradigms

Make sure your knowledge is up to date. If you where involved in a bigger redesign 3 years ago, it is probable that there is new knowledge and design paradigms. We had a huge change of design paradigm 4-5 years ago, when the whole industry moved from table-based to css-based design. We are now seeing changes in how we use scripting in webpages with ajax, mashups and external apis. There is no need implementing new stuff, just because you can, but it is important that you expand your knowledge. You never know when you will need that knowledge.

Surveys and Usability Studies

If you need answers to a lot of questions regarding the user interface, there is no such thing as speaking directly to the customers. If you have access to surveys or usability studies, I suggest reading them closely and try to extract everything you think is of importance for the front-end architecture.

Design

Is there any mockups on the upcoming website? Often designers design a mockup for start-up meetings of bigger redesign projects. These designs may say something on what to expect of the design. Is there anything in the design that you think will impose a problem for you?

Other

Depending on your website, the time-frame for the redesign project and other parameters a pre-study may analyze a lot of different aspects of potential issues and possibilities for the front-end architecture.

Deliverables from a Front-End Architecture Pre-Study

Typical deliverables from a pre-study may be recommendation on technical platform, guidelines for the user interface, prototypes of certain business processes, proof-of-concepts on technical solutions.

Next article will focus on the Front-End Platform, and we start with the server side part of the front-end architecture.

30 Articles on Front-End Architecture

This article is the first in a series of 30 articles dedicated to Front-End Architecture. I have been working with front-end related tasks for more than 10 years and realized that I haven’t documented my findings very well. This project will change that.

In this series of article the focus will be general and the use-case, or scenario, is a bigger redesign (hardware, software, design and user interactions) of a high traffic web. The issues raised and answered in these articles is applicable on projects where everything is made from scratch as well. The goal is to put a lot of my findings and experience on paper and to share the knowledge I have that may help someone facing architectural decisions within the front-end area.

The first question in this series of articles is What exactly do you mean when you talk about Front-End Architecture?. There is no simple answer to the question, but I will try to answer it here in brief and in the series of articles in detail.

I believe that Front-End Architecture deals with everything that is in some way user-oriented. It is not as simple, as to say that front end architecture is the presentation layer in an application. A lot of times user-oriented tasks has effects on a big part of the system you are building. In my profession I have always tried to focus on things within and above the business layer. A lot of decisions made in the front-end may effect data models and choice of server software and such things, but I try to stay out of those areas, as I am certain that there are people enjoying those issues and does it better without my involvement.

Things I have worked with in my profession as Front-End Architect:
- Business logic in Java
- Business logic in VB.NET
- Business logic in PHP
- GUI logic in JavaScript
- GUI logic in Java
- Definition of data models for XML or JSON transfer
- Definition of API:s for 3rd party developers
- Analysis of MVC-frameworks
- Analysis of Presentation Engines
- Analysis of Server Side Libraries
- Analysis of Client Side Libraries
- Analysis of Clients
- Analysis of Mobile Clients
- Analysis of Competitors
- CMS Analysis
- Performance Reviews
- Documentation
- SEO
- I18n
- L10n
- Troubleshooting
- Payments
- User Interaction Design
- Use Case Definitions
- Mockups
- Prototypes
- Requirement Specifications
- Requirement Analysis
- Research
- Usability Studies
- Statistics
- A/B Testing
- Business Processes
- Conversion Rates
- CSS
- Ajax
- Semantic Markup
- Microformats
- Affiliate Integration
- Cowboy (NS4)
- Sumo-wrestler (IE)
- Kamikaze Pilot (Maintain JavaScript by programmers with too much ego and too little knowledge)

The list may grow during the articles. From the next article we will start focusing on some of the areas listed above. The first article will be on “Front-End Architecture: The Pre-Study”.