Smart phones as thin clients

Government Computer News ran an article in its May 26 issue that looked at the recent crop of applications being developed for smart phones (GCN.com, Quickfind 1117).

Whether custom-built or designed for consumer markets, the majority of applications — from first responder applications to customer relationship management tools — are developed to run on a specific device, whether it is a BlackBerry, Windows Mobile smart phone or other device.

But that development model has certain trap doors, said Nick Intintolo, vice president of sales and marketing at Karya Technologies.

The first problem is that you might have to develop the same application multiple times for different platforms. “What happens if you have a segment of Black- Berry users, another segment of iPhone users, and another segment of Treo or Windows Mobile device users?” Intintolo asked. “You are really starting to create an inefficient development architecture. We are sort of going backwards in time, back to the days when we were building systems on Big Iron and creating a lot of legacy databases and legacy applications.”

Karya Technologies and a handful of other developers are pursuing a different strategy: Why not do the application development on the server side and deliver it to a thin-client application on the portable device?

That, in fact, is what Karya’s MobileReflex does: It grabs data from the Web services of existing applications running on a network and converts it. If you want to change the data delivered to the devices or, say, integrate new applications, you don’t have to design a new client for each mobile device platform. Instead, you simply make the changes in the MobileReflex software running on your servers.

“Rather than building custom applications over and over and over again on these different devices,” Intintolo said, “we solve the problem by creating a hub-and-spoke architecture where the server administrator functions as a hub.”

Although building applications specifically for clients might make sense for certain applications, Intintolo said many enterprise-level applications have footprints that are too big to squeeze onto smart phones. “We’re dealing mostly with metadata,” he said. “We’re not looking to take on a significant amount of data handling because we know that that would be excessive in a BlackBerry.”

Intintolo emphasized that Karya’s solution uses open-source software. Research in Motion “is really, really pushing to say, ‘Hey, adopt our development language.’ We say there are already languages out there that are just fine.” — Patrick Marshall

Guidance for securely using SSL VPNs, mobile devices

The National Institute of Standards and Technology has released a guide to virtual private networks that use Secure Sockets Layer technology, comparing and contrasting them with IPSec and other VPN solutions.

Special Publication 800-113, “Guide to SSL VPNs,” includes recommendations for designing, implementing, configuring, securing, monitoring and maintaining VPNs.

NIST also released for comment a draft version of SP 800-124, “Guidelines on Cell Phone and PDA Security.” It is an overview of common cell phone and personal digital assistant devices to help administrators make informed information technology security decisions about their use.

VPNs that secure connections for remote users via Web browsers and SSL encryption are popular because they are easy to use. The SSL protocol is included in all standard Web browsers, so the client usually does not require reconfiguration and users can access the VPN from a wide range of computers. Portal VPNs enable users to access resources via a Web site. Tunnel VPNs allow users to access applications and protocols that are not Web-based but require the browser to handle active content.

“Despite the popularity of SSL VPNs, they are not intended to replace Internet Protocol Security VPNs,” the NIST guide states. “The two VPN technologies are complementary and address separate network architectures and business needs.”

Requirements and recommendations for deploying an SSL VPN include:

* Configuring it to allow only cryptographic algorithms and modules that comply with Federal Information Processing Standard 140-2.
* Evaluating several products against clearly defined requirements.
* Using a phased approach to planning and implementation.
* Recognizing the limitations of the technology.
* Implementing other measures to support and complement the VPN.

“Guidelines on Cell Phone and PDA Security” provides an overview of security considerations for a class of personal, mobile technology that is becoming increasingly powerful and important in the workplace. Small devices now include much of the functionality of desktop computers and mobile communication features such as Wi-Fi, Bluetooth, multiple forms of cellular service and Global Positioning System receivers.

The devices can be easy to lose and subject to malicious code, spam, eavesdropping, tracking and spoofing.

“To date, incidents from malware and other identified dangers that have occurred against handheld devices have been limited when compared with those against desktop and networked computers,” the guide states. “One factor is that no single operating system dominates handheld devices to the same extent, fragmenting the number of potential homogeneous targets.”

But to avoid problems, NIST recommends that organizations:

* Plan for and deploy appropriate security controls for cell phones, PDAs and other handheld devices.
* Ensure that devices are deployed, configured and managed to meet business objectives and security requirements.
* Manage and maintain the security of devices throughout their life cycle.

Comments on “Guidelines on Cell Phone and PDA Security” should be e-mailed by Aug. 8 to 800-124comments@nist.gov with “Comments SP 800-124” in the subject line.

Basic Tab Concept Phone

Another concept design, this time by Jaren Goh and something different in terms of looks and features, none of which have been stated, the aim was to design a handset which would blend into current fashion and everyday life.



Not relying on high end features or ground breaking technology this is much on the side of lifestyle.

The heart of the design for this mobile phone does not lie on the technological advances it had in it. It was designed to complement our fashion and the way we dress and not to evoke too much technological gadget traits. On the front lies a lush wide black screen and nothing else to steal anything away. It resides on a metal slab to add volume and a premium touch to it. A better way to show how this design correlates to fashion is the camera tab on the back. Instead of having it looking like camera shutter or lens cover. It was designed using features found on handbags and fashion accessories that is so everlasting.

With a blend of sophistication and style it is a great concept not evoking too many eye catching features which would make it stand out. I personally think it looks pretty futuristic and cutting edge.

Hands on Pics of iPhone 3G

The first hands on pictures of the new iPhone 3G have been circulated.



Both Laptop Mag and iLounge have done some reviews on the device. Some simple tests like 3G speeds and build are mentioned, highlights from both websites respectively below:

via Laptopmag

Speedy Browsing
After checking out the new hardware, it was time to put the 3G to the test. It took about two seconds to transition from Wi-Fi to the 3G network. I tested out the speeds on three sites: It took the phone 4 seconds to load www.laptopmag.com, 2 seconds to load cnn.com; 3 seconds to load www.nytimes.com. Pretty damn speedy.

Swift GPS Connection
I couldn’t get the best handle on the GPS here in the convention center. But I was able to bring up a map of the San Fran area. According to an Apple rep, turn-by-turn directions will be available through the Maps program. Above the map was a button to find “current location.”

via iLounge

Unlike the original iPhone, which has proved much more resilient to the sorts of scratches and scuffs that plague iPods, the iPhone 3G’s shell is indeed just glossy plastic with a thin layer of clear coating. It’s not ceramic, as some might have guessed, and not covered in a magic material that won’t scuff: as a result, you can expect to see marks similar to the ones on first-generation iPod nanos and fifth-generation iPods, all over again. The black version, as shown here, picks up fingerprints and smudges at an impressive rate; we wish we’d been able to take some pictures without the smudges. Ironically, the white plastic color that Apple discontinued for iPods may wind up being the most attractive color for new iPhones, especially after spending a few days in a pocket or purse.