Jun 01

Companies have been sampling products to their potential customers for ever. When you can give them a nibble of your product or service and add to that a sense of urgency, you may be on to something.

Recently, Adobe released public preview versions of some of their upcoming programs that will be available in the Creative Suite 4 (CS4).

That they released preview versions of their software isn’t all that new … but the time-limit they put on the installed preview, before the program is disabled is quite surprising … two days!

With the standard software trial period being 30 days, or in some cases unlimited time - limited features, Adobe has played a unique hand that has many people in the graphic community scratching their heads; why offer a trial of their software that only lasts two days?

Exclusivity and Urgency

When google first released Gmail, they made it available to only a select few. Those that got an account were given a handful of invites to give out to their friends. You started with one invite and a little message above your invites indicated that you would get more eventually.

This limited supply caused the invites to be cherished like gold; you only gave them out sparingly. It also created an automatic digital divide between those that had, and those that had not. There was a sense of pride in the fact that you got a Gmail account and that through your mercy, you could freely share this rare resource with those you liked the most.

The demand and short supply fueled the social media fires; the word that Gmail was out became very viral.

Adobe has provided fuel for a similar type of fire by allowing a very short window of time to preview their apps. There is also a sense of hiearchy being built between those with registered copies of CS3 ( wo can enter in their CS3 serial numbers and keep the CS4 versions alive, and those who don’t have CS3.

Two days is a very narrow window to dig into a program, but the hope that it will generate some buzz, a sense of demand for the new features and more peviews to come seems to be working. The graphic community has brought it upon themselves to blaze, like Paul Revere, through every graphic forum, user group and chat room to announce that the betas are available.

written by socialplasm \\ tags: ,

May 24
Old Skool

Recently I wrote about how many programmers would kill for the ability to work uninterrupted by clients.

Well, the flip-side of that is that not all business-type people think that working with developers is a walk down happy time lane either.

The truth is that there are distinct types of personalities that fit the role of programmer/developer and there are certain character traits that make up the general population of business-type people; both sides have exceptions to the rule, of course. But the generalizations do hold some water.

Fact of the matter? Most business people don’t have the time to learn the ins-and-outs of Microsoft Word let alone what it takes to put together a website. Most don’t have the capacity to learn to speak in one’s and zero’s; we’re talking about specialized skills on both sides of the line.

‘Tech’ was out of reach for many … until now

There has been a drastic change in the accessibility of web development since the introduction of blogging technology.

Blogs enabled anyone to have a presence on the web. Shortly after the concept took off, companies like WordPress made it even easier for those less technically inclined to get in the game.

WordPress and other content management systems (CMS’s) made it very easy to bridge the gap between having to know how to program and wanting to have a web presence.

In addition to the technology being easy for public consumption, many in the development world realized that there was a whole new niche of development to be had; develop programs open-source and give them away. The return for the programmer? High levels of visibility, access to new and unique projects and jobs based on the business community’s interaction with your free and accessible plugins and applications and a new working environment; a client-free development model.

What Does this Mean for the Non-Programmer?

The majority of the people in the blogging community are just regular people; not uber-geeks who can create things out of one’s and zero’s.

How did they get started? How do they make it look like they know how to build a website?

Here’s a recipe for building a FREE website:

  1. Go and sign up for a WordPress account. A WordPress account will set you up with your own, free, easy to manage website.
  2. Make it pretty by choosing a new theme for it. A theme is a fast and free way of ’skinning’ your site with a new look and feel. Log into your free wordpress account and you can search and install any one of thousands of free themes.
  3. Log in start and writing blog posts.
  4. There you go! You have a FREE Internet presence!

Thanks, but I am a little more motivated. I want my site to Rock!

Ok, read on…

written by socialplasm \\ tags: , ,

May 23

I know many programmers who confess that the best business opportunity they could imagine would be one where they weren’t constantly bothered by their clients.

I don’t build in order to have clients. I have clients in order to build.
-Ayn Rand

Enter, a new business relationship: coding for open source platforms. That’s right, programmers that have caught on to the vision that if they write code, plugins, themes or other elements for platforms such as WordPress … for free … that they actually make as much money, if not more, as they would working on a more transactional client-based list of projects.

Old Skool

The old school model of development projects for clients (client approaches developer, developer does work, client pays for work) is still strong, and probably won’t go away any time soon. This new client-free model can supplement, and in some cases, completely replace the project-to-project routine that many programmers and developers find themselves in.

Old Skool

The Programmer’s Pay-off

Here are 10 steps to how the new method of developing free or low-cost projects for the open source community can impact a programmers pocket book. We’ll use programming a free plugin for WordPress as an example:
  1. (Identify) Programmer sees a need within the WordPress blogging platform
  2. (Contribute)Programmer takes 3 hours on a Tuesday night and writes a nifty plugin for use within the WordPress community to fill the need
  3. (Announce) She posts it on WordPress’ page to let the community know it’s out there and available for download
  4. (Distribute) She creates a page on her own blog, puts the plugin on there for download
  5. (Communicate) She goes out to the communities where she can tell people that her plugin can fill their needs
  6. People follow her links back to her blog and download the plugin
  7. Over a short bit of time the plugin gains some traction and a community of users and supporters is built
  8. As a result, businesses contact her about writing a similar app, with some tweaks, for their internal website
  9. She contacts them and provides a proposal
  10. Project approved, she takes the check to the bank
This type of development means that a developer can program something once and have the influence felt more wide-spread than if they were to develop ‘for’ an individual entity.
Old Skool
It may seem like an over-simplification of the process; ‘build it once, benefit the masses’ … but the idea is that by contributing and distributing in small, measured efforts to the open source community, or pro-bono for a widely-used platform like WordPress, your mad skillz have the potential to gain exponential visibility amongst those that are looking for good developers for their own projects.
Additionally, your free plugin may become the ‘lite’ version of a more robust plugin or app that you choose to build down the road based on the success of the free version.

written by socialplasm \\ tags: , ,