In mature markets, the mobile Web, along with associated Web adaptation tools, will be a leading technology for B2C mobile applications through 2012, and should be part of every organization’s B2C technology portfolio. (Gartner, 2010)

If you are interested in further reading, here is the direct link to their press release.

There is, of course, never an appropriate time to leave. I feel a great sense of accomplishment building several successful intranet, extranet and mobile products. The projects and platforms that I have been closely involved with have found amazingly good homes within the company. What I loved most about my tenure is the opportunity to collaborate with some of the smartest and most passionate engineers in the industry to develop some great products that our customers love.

Before starting my next endeavor, I will be taking a few days off to enjoy the nice spring weather in Atlanta.

I’d love to stay in touch via LinkedIn.

Update (April 3rd) - Here is a news about me in a Turkish newspaper today. Very cool!

Traditional practices did not stress the need for innovation, but business now runs very differently than it did in the past. Boundaries no longer exist, and we play on a global field, where unforeseen changes in the marketplace and the competitive climate can arise at any time. (Hoque, 2010)

It is not only because we enjoy the flexibility and the heightened responsiveness that agility provides, but also because agile practices empower the innovation with the customer-centric approach.

• The Five Dysfunctions of a Team: A Leadership Fable by Patrick Lencioni
• The Five Temptations of a CEO: A Leadership Fable by Patrick Lencioni
• Death by Meeting: Solving the Most Painful Problem in Business by Patrick Lencioni
• Founders at Work: Stories of Startups’ Early Days by Jessica Livingston
• Programming Pearls by Jon Bentley

I actually started reading the last two before and made both of them to almost halfway, so it will be about one book every three months. We’ll see how it goes.

If same issue occurs in an ASP.NET 3.5 SP1 application, you can use the StopRoutingHandler class which implements the IRouteHandler interface.

Update - I don’t have any Myspace account either.

Update - I am not against any social networking, it is just my personal preference at this time.

If your application requires local processing and must work in an occasionally connected scenario, consider designing a rich client. A rich client application will be more complex to install and maintain. If your application can depend on server processing and will always be fully connected, consider designing a thin client. If your application requires a rich user interface (UI), only limited access to local resources, and must be portable to other platforms, design an RIA client.

Determine the device types you will support

When choosing which device types to support, consider screen size, resolution (DPI), CPU performance characteristics, memory and storage space, and development tool environment availability. In addition, factor in user requirements and organizational constraints. You may require specific hardware such as a global positioning system (GPS) or a camera, which may impact not only your application type, but also your device choice.

Design considering occasionally connected, limited-bandwidth scenarios when required

If your mobile device is a stand-alone device, you will not need to account for connection issues. When network connectivity is required, mobile applications should handle cases when a network connection is intermittent or not available. It is vital in this case to design your caching, state management, and data-access mechanisms with intermittent network connectivity in mind. Batch communications for times of connectivity. Choose hardware and software protocols based on speed, power consumption and chattiness, and not just on ease of programming.

Design a UI appropriate for mobile devices, taking into account platform constraints

Mobile devices require a simpler architecture, simpler UI, and other specific design decisions in order to work within the constraints imposed by the device hardware. Keep these constraints in mind and design specifically for the device instead of trying to reuse the architecture or UI from a desktop or Web application. The main constraints are memory, battery life, ability to adapt to difference screen sizes and orientations, security, and network bandwidth.

Design a layered architecture appropriate for mobile devices that improves reuse and maintainability

Depending on the application type, multiple layers may be located on the device itself. Use the concept of layers to maximize separation of concerns, and to improve reuse and maintainability for your mobile application. However, aim to achieve the smallest footprint on the device by simplifying your design compared to a desktop or Web application.

Design considering device resource constraints such as battery life, memory size, and processor speed

Every design decision should take into account the limited CPU, memory, storage capacity, and battery life of mobile devices. Battery life is usually the most limiting factor in mobile devices. Backlighting, reading and writing to memory, wireless connections, specialized hardware, and processor speed all have an impact on the overall power usage.

Reference: Codeplex (Microsoft Patterns and Practices)