Help The Victims of the 8.9 Earthquake in Japan by Spreading Awareness and Aid. Visit https://american.redcross.org/site/Donation2?idb=0&5052.donation=form1&df_id=5052 to donate and provide your generous support.

God Bless.

1. Social Marketing: Facebook and twitter will rule next year (or next few years too). Every SEO company which helps their client to succeed online, should help them by letting them to consider these technology giants, which might take them to next level. Social media optimization will not replace Search Engine Optimization, but social media optimization should go in parallel with SEO.

2. Cloud applications and hosting: We started using invoice applications first (Freshbooks) and it ended up with cloud hosting. We moved our sites to cloud. Also helped clients to taste the flour of clouds. Web hosting with Amazon web services was a very different service we offered to our clients. Setting up their sites and web applications with EC2 were initially needed some learning with Amazon, but it became an expert service at the year end. In 2011 we will be providing setting up applications in cloud as a key service.

3. Social Media integration: We learnt FBML, Facebook SDK with PHP and started offering business pages and applications with Facebook , which will continue next year. Marketing those pages is another fruit to reap. Similarly Facebook Like button integration and Twitter API integrations are two important promotional services clients will require in 2011.

4. Blogging: Is blogging dead? No, it has come out in different format. Twits and Facebook status updates are micro blogging and People who do not want to write much, or those who like to share instantly use them. But, still business blogging isn’t dead. Macronimous helped serveral clients to start blogging. WordPress helped us much. We provide SEO friendly WordPress blogs by adding SEO plugins and basic SEO readiness setup as a mandatory feature along with every blogs.

5. Search Engine friendly coding: SEO readiness is no more a value addition. Every site we develop should be ready to for Search Engines. It begins with light weight coding and ends with Keyword setup. Making dynamic sites such as CMS driven content, ECommerce sites and Flash sites with PHP and .NET are offered by us as an expert SEO service.

6. HTML5 for Flash: We started offering HTML5 based presentations and sites. Flash was replaced by jQuery for many clients and they were happy too. By 2011, HTML 5 should be the standard, and Flash will move for interactive applications. The test results made at RWW in March 2010 was an eye opener. With full fledged CSS3 and HTML5, easy to create interactive web applications without Flash should be feasible.

7. Rich Internet Application – Flex was used much in few projects this year. We look forward to work on RIA based frameworks, such as Sencha.

8. PHP Frameworks: We used Codeigniter very much. But MVC is still not very popular, and framework based applications are relatively lower then non MVC based solutions like WordPress etc.

9. Smartphone and Tablet applications: We did much with iPhones this year (including 2011 World Cup Cricket app), moving to iPads. Android development for Smartphones and tablets will be our important strategy for 2011. By the end of this year, we see more Tablets, and thanks to iPad, which regenerated the new platform of business. Building portable applications for the mobile and tablet browsers is another channel. By providing mobile friendly websites we help clients become accessible everywhere. Sencha Touch nd dhtmlx’s JavaScript mobile UI APIs will be a part of the development in 2011.

10. Security for Opensource applications: Many of us believe that Opensource application based development cost is almost nil. This is a lie. The initial cost of a WordPress or Joomla based application/site development might be relatively lower than a closed, custom application development. But the real cost of ownership is affected by the security issues that comes with the Open standards, mainly when they are affected by Security attacks. We will work hardly on providing secure web applications when we develop them with open source in 2011. Even at this year end we have an important announcement with a  major security fix from WordPress.

11. Remote project management: Managing projects across the globe was a real challenge a decade ago. Using standards and web based project management tools we provide hassle free project management. Tools like Basecamp, dotproject and Eventum helped us much, and we are working with few cloud based PM and collaboration tools, github etc. Apart from this our agile based PM methods have had some customization. Part of that is a project closure questionnaire.

Overall, many easy and hard ways of learning helped our team to build the next year strategy very much. Leave your comments if you had such learnings to share with others. Looking forward to another technologically challenging year which helps us to help our clients.

Dilbert stripe: © Dilbert.com

CodeIgniter

Now is the real time to know about the power of Codeigniter. So ignite yourself and initiate reading to know why you want to choose Codeigniter. It will suit if:

• You require a framework which can be set up very quickly and efficiently.
• You need an outstanding performance.
• You are a developer who needs methodical and clear documentation.
• You need a framework that does not call for sticking on to restrictive coding rules.
• You want a framework that needs nearly zero configuration.
• You need a framework which is compatible with many environments

Some of our developers always prefer to use  CodeIgniter, write me if you want to see some samples and know why they used CodeIgniter. If you want to start using CodeIgniter start right here at: http://codeigniter.com/

3. Frameworks we like: 2. CakePHP and why?

2. PHP Frameworks we like 1. Zend and why?

1. PHP Frameworks we like

Working with PHP is something you enjoy everyday!. You always wanted to do your best to your clients. But when the deadlines are pressing and when the clients are on your shoulders people start doing messy codings, and the standards got ignored. But you practice the best ways of programming everyday, it becomes your style and you have no alternate choice of doing quick and dirty work. Here are some simple best practices discussed by Matthew Weier of Zend technologies. Use them when you get an opportunity, and they will become your style of programming.

But as the years passed by, the requirements too changed. When people started working collaboratively, (which was made much easier with the internet and with bandwidth growth) people slowly started moving into web based applications. Web based Emails are possibly the first web applications we used. Software companies started developing cross-browser compatible web applications. At a point, We stopped application development with Visual Basic and started focusing only on ASP and then ASP.NET. Now Web 2.0 has changed the perspective of ’software’ totally. And Hybrid applications became possible with APIs etc.

Likewise, in Mobile development, there are two ways to create  applications. (1) Mobile browser based applications – which are websites optimized for Mobile browsers and (2) Installable (or Native) Mobile applications.

They both have advantages and disadvantages.

Why Mobile Browser based applications and why not?

So, in short: The advantage of a mobile browser based application is the low development cost, and the disadvantage is the bandwidth limitations and the limitations of Mobile websites, which does not access your Phone’s components like your Address book, Camera, etc.
Mobile Brower based applications are slow due to the bandwidth limitations and will eat up your data usage in your phone plan. Also, the user needs to remember the URLs and type it, which every cell phone user knows is just plain  hard. One advantage is that the development cost is low since the developer only needs to consider how to make it compatible with most mobile browsers, and not each type of cell phone. Also, now that many Mobile browsers support HTML and smart phones come with bigger screens to see full sized websites, and users can zoom in and out. We have keyboards too to manage this. But, if you want to browse websites, you can do that in your tiny Netbook, which you always carry with you, right?

So, in short: The advantage of a mobile browser based application is the low development cost, and the disadvantage is the bandwidth limitations and the limitations of Mobile websites, which does not access your Phone’s components like your Address book, Camera, etc.

Why Native mobile applications and why not?
Native (installable) applications resides in your cell phone, and you  launch it directly from there, with whatever search parameters  are stored within your mobile (Eg. The names of the 50 states in the USA, your favorite locations, daily weather, etc). Except for free text search, all of  the search parameters can be stored in the mobile – OR they can be updated just one time.  The communication between the Data/Web server and the mobile phone could be drastically reduced. An application like a stock portfolio can be created within your Phone and stored. Every day you just need to update the stock prices. You need not download the entire portfolio each day. Also, the application resides within the phone, and can access your phone’s features such as your camera, phone book /contacts, etc.

It has also quickly become clear that another  hidden advantage of native applications is brand loyalty. If a customer installs a mobile application which you supply, he or she will rely on your application and trust it. For Example, I use Viigo for regular information updates (News, weather, etc) but a site called Justdial.com or Google local for local address research. If Justdial comes with a Blackberry solution, they captured me as their user.

The disadvantage is obviously the development cost. No two mobile platforms can share the same mobile application, and there are too many Mobile operating systems (or platforms) existing in the market. If you develop a mobile application to market it widely, you need to develop that in J2ME (for phones that support only Java with no loaded OS), Symbian, Mac iPhone, Android, RIM, WebOS( for Palm pre), LinMo and Windows mobile. Though J2ME (or Java ME) is widely used, it has  severe graphic limitations, and I am sure it won’t be pretty  in my Blackberry Bold! If a developer does not have expertise in more than one technology, then you need to use various mobile developers, and finding them all under one roof would be difficult.

So, in short: The advantage of native mobile applications is quick access and less data transaction, and the disadvantage is the cost of development.

Hybrid mobile applications?

No, “Hybrid” applications are not ways of  ‘going Green’ or developing applications to be ‘environment friendly!’

They are Applications that use BOTH browser interfaces and native mobile components. With HTML5 and JavaScripts, now the browsers are becoming capable of accessing a phone’s built in features like contacts, camera etc. We started developing applications using PhoneGap and I believe solutions like this should, hence the name, fill-in this gap.  Platform free mobile solutions are what we need now and the gap between the browser based applications and native mobile applications is getting narrower.

Finally, what would be the disadvantages of  hybrid mobile applications? Two things comes to my mind…(1) Application security, and (2) the learning curve for the developers. Mobile developers need to know HTML and Web developers need to know mobile phone APIs. Right? Let us see how these obstacles are overcome.

1. Test, Test and Test your applications before you send it to QA team

2. Fix all the bugs which you find

3. Remember this: If you forget to include QA in the project schedule and swallow QA time by extending your development time, you are doing injustice to the client, your employer and the worst is to yourself.

3. Fix all the bugs which QA team finds

4. Assure yourself that you leave no faults in your application before sending it to the client

5. Do NOT expect the customer to test your application for yourself. The customer need not be a Testing professional.

6. Make the list of changes and bugs reported by the customer.

7. Schedule them – and Let the customer know the turnaround time to fix them all.

8. Fix them and let the QA check them.

9. Make sure that you make the customer happy, and let him prefer him as your favorite developer.

10. Learn from the bugs; By not repeating them you can become a super developer.

11. If a project has strict deadlines, it needs strict QA.

12. Avoid reporting the known bugs to the client – instead fix them!

As I said learning never ends. So, I welcome if your valuable rules or strategies or comments could extend this list are welcome. Shoot them them as your comments.

We have our iPhone application successfully approved by apple and available in iTunes.  The application’s purpose is to bring different love tools under one roof. With our first version, we have included four different modules and we are planning to bring more features in our future releases.

Our first tool is “Love Chart” where you can check the relationship you might have with your partner(s). Our Next tool is “Compatibility Chart” which helps a person to find their compatible, incompatible and neutral partners, using their moon sign. We believe this might help you in zeroing in on your mate. The next tool is “My Partners” using which you can preserve memories with whom you have spent time together. Our final tool is “Gender prediction” which helps a couple to predict gender of their baby they are going to have, using mothers age and month of conceive. The couple can also decide the month the mother has to conceive, to have baby of their own preference.

We developed the application using XCode 3.1 IDE tool to program our logic and interface Builder to design our interface. Since this was our first application, we went through almost all the video tutorials available from Apple’s Developer Site which taught us what is iPhone application development all about. We then started with learning Objective C programming. Finally we went through the Human Interface Guidelines, which is essential when you develop any iPhone application. With this base knowledge, we dived directly into our first application and successfully got it approved by apple without any problem.

We are working on our next application in the same Lifestyle category and it will be available soon in iTunes store and you can check this site for more information. You can expect more from this before this year end. We will keep them posted.

You can buy My Love Vault from:

Now let us see why you should avoid duplicating the content?

First of all, copying the content brings down the understanding of the concept. If you start understanding, that is only how you grow. The scriptwriter should understand why something is and how it works. If you copy, you are missing out on that. You are just resurfacing the upper layer and not getting into layers underneath when you do that.

If you are not willing to write on your own, you will not know the exact intention and get stuck at one place. You will not know how to take it forward. The originality of the content will be missing.

While it is easier to just copy from someone else, why do you have to create a new one? If you don’t do that, you will not know why it looks like, you cannot feel the way it feels like and you will not be able to read the way it should be read. The final outcome will be an artificial one.

Content Duplication and its impacts on SEO

1. Duplication of content will be considered a spam by all the search engines. There are so many websites with similar products, so the copywriter must be very careful in creating content. Search Engines likes fresh and unique content. It ranks websites depending primarily on the content used in web pages. 

2. Changing the phrase of an existing content and rewriting is also considered as content duplication. Search Engines have ways to find out and it is supposed to be spam. This will certainly affect the ranking of a website.

3. When a website is reported to have duplicate content issues, the total number of pages ranked by the search engine will automatically come down. Fewer pages to rank will lessen the rankings and might lead to lower traffic.

4. It is important to make your content unique; otherwise there is absolutely no point in doing all these. The search engines will not bother to feature your website in its result pages.

5. There is a difference between content duplication “penalties” and “filtering”. When we refer to penalty in search engine rankings, we actually talk of points being reduced from your overall score, but the truth is, the pages are just filtered like you filter unwanted particles from a can of liquid. Accidently, this filtering can sometimes filter out your good particles.

Tips to avoid Content Duplication

1. While preparing content, make sure you don’t copy it from somewhere and try to replace the words with exact meanings. The search engines have already come up with a solution to deal with this issue.

2. Before you sit down to write, ask yourself what exactly will create value for your users.

3. Try to get various perspectives, take the good points from them and fill the rest with your own thoughts and creativity. After all, you have to make it happen and move forward.

4. You can be influenced by many, but make sure you don’t copy anything.

So while preparing content, watch out for duplication from search engine’s point of view and as well as loyal customer’s point of view. At the end of the day, it is the search engine and ultimately the customer who are going to “look” at your content, so make sure it is liked by both, otherwise all the efforts you put in for your business to grow will go wasted.

The process goes this way:

1. Register and get an Apple ID
2. Apply for the iPhone developer program and wait for them. It took 15 days for them to contact us back.
3. Send your company incorporation to Apple with the registration ID by Fax. They provided 3 Fax numbers.
4. After Faxing, I also sent them an Email. Received an acknowledgement the next day from Apple.
5. Again, a waiting period, 8 days.
6. I wrote them again.
7. Got a call from Apple Hong Kong within an hour and then the agreement form by Email within another hour
8. Sent the agreement to them (Just a click to agree). It took me to a print form to send the credit card details. Printed it, filled it up and sent by Fax.
9. Next day, payment was processed, and we are allowed to access the iphone developer portal.

Everyone says that it’s not easy to join in the developer program. Actually its right partially, But Apple wants to allow only serious developers in. Their verification system is but time consuming, and they really want to see if the developer is providing complete details. I like this verification system, which filters non-serious developers.

Ok, now why take all these steps?

Here is the list of iPhone development program benefits.

1. Develop and test it on the actual device (iPhone or iPod Touch) – You can only test the application in the simulator, until you become a member.
2. You can distribute your application or game through iTune store for free or for a price.
3. Share your application with other iPhones (up to 50) for internal testing – called ad-hoc distribution
4. Coupon code for your application reviewers

Overall, your application is reaching millions of iTunes store users, and you get a chance to reach them easily.

I believe now RIM is also working on a store like this (http://mobileapps.blackberry.com/devicesoftware/entry.do?code=appworld) to support Blackberry developers.

www.youtube.com/watch?v=QJncFirhjPg

It was presented in an attractive way – at the end of it, I am sure, you will know the basics.