Step By Step Example for How to Run The Derby DB and a Sample Code that Uses it
This short video clip explains how to run the Derby DB (Java DB) and how to compile and run a short Java code that connects it.
This short video clip explains how to run the Derby DB (Java DB) and how to compile and run a short Java code that connects it.
iPhone application usage reaches its zenith on nights and weekends according to new data issued by mobile analytics platform
Localytics. iPhone app behaviors reach their peak at 9 p.m. ET on weeknights, Localytics reports, adding that usage ramps up slowly over the course of the workday and then tops out when East Coast consumers are at home and their West Coast counterparts are commuting from work. iPhone users generate 7 percent greater traffic on weekends than during the average weekday–Saturday traffic is at its lowest ebb at 6 a.m., but accelerates to over 90 percent of peak usage by 11 a.m., remaining at or near its apex for the duration of the afternoon and evening.
Localytics concludes that while the iPhone is making professional inroads, it remains a personal device for most users, adding that the results of its study bode well for Apple’s forthcoming iPad tablet device. According to Localytics, the data suggests that consumers looking for entertainment, trip planning, sports updates and music services are already reaching for devices that are smaller and more convenient than their desktops and laptops, indicating the release of the iPad could further galvanize those behaviors.
For more on the Localytics study:
- see this chart
- read this release
Related articles:
Apple cracks down on adult-themed iPhone apps
App Store project starts triple following iPad frenzy
Microsoft is serious about making a fresh start in mobile–last week, Windows Phone Application Platform & Developer Experience program manager Charlie Kindel confirmed existing Windows Mobile applications will not run on the forthcoming Windows Phone 7 operating system, news a fellow Microsoftie first let slip late last month. “Windows Phone 7 Series is different because we reset everything we were doing to focus on end user experience. This extends directly to the developer platform,” Kindel writes on his Windows Phone Development blog. “To enable the fantastic user experiences you’ve seen in the Windows Phone 7 Series demos so far we’ve had to break from the past. To deliver what developers expect in the developer platform we’ve had to change how phone apps were written. One result of this is previous Windows mobile applications will not run on Windows Phone 7 Series.”
Kindel promises that Microsoft and its partners plan to keep delivering and supporting new devices based on the current Windows Mobile 6.5, adding that expertise and familiarity with the software giant’s tools are not squandered. “If you are a .NET developer today your skills and much of your code will move forward,” Kindel states. “If you are a Silverlight or XNA developer today you’re gonna be really happy. New developers to the platform will find a cohesive, well designed API set with super productive tools… Our mission is to help developers go after the next generation of mobile customers with an amazing set of tools and technologies. Developers will be able to bring new kinds of content to more screens and markets faster.”
Remaking Microsoft’s mobile identity is undoubtedly a positive and necessary move, and new distribution channels and accelerated paths to market are also welcome advances for the Windows Phone developer community. But for now, those developers are in limbo, waiting for the Windows Phone 7 SDK to drop and devices to ship while Windows Mobile 6.5 continues its inevitable slide into irrelevance. Developers are caught between Microsoft’s future and its past, with few options for the present–beyond channeling their creativity into applications for rival mobile platforms, that is.
But while it would appear there is little incentive to create or improve consumer applications for Windows Mobile 6.5, enterprise software could pose a viable alternative. Microsoft’s Mobile Platform Services Product Management senior director Todd Brix tells the Seattle Post-Intelligencer that WinMo 6.5 will be positioned as a more affordable workplace solution, with Windows 7 smartphones marketed as a hipper, more expensive consumer product. Time will tell just how long Microsoft will continue actively supporting Windows Mobile 6.5, but giving it a distinct, enterprise-centric raison d’être separate from Windows Phone 7 represents another positive step forward as the company continues to regain its balance. -Jason
Books now outnumber games in Apple’s App Store, marking the first time the games category has failed to dominate total iPhone and iPod touch applications, according to new data issued by mobile advertising exchange Mobclix. As of last week, the App Store boasts more than 26,500 books, representing 18.6 percent of the total 142,000 available applications–the storefront features a little over 25,000 games, or 17.6 percent of all apps. Article
Google announced the launch of the third release of its Android Native Development Kit, enabling developers to target smartphones running Android 1.5 or higher. In addition to the usual bug fixes and improvements, Android NDK r3 enables applications created for Android 2.0 to directly access OpenGL ES 2.0 features, granting developers the flexibility to control graphics rendering through vertex and fragment shader programs via the GLSL shading language, theoretically paving the way for 3D gaming.
Android NDK r3 also boasts toolchain binaries refreshed with GCC 4.4.0, which should generate slightly more compact and efficient machine code than the previous 4.2.1. “Note that the GCC 4.4.0 C++ frontend is more pedantic, and may refuse to compile certain rare and invalid template declarations that were accepted by 4.2.1,” writes Google’s David Turner on the Android Developers Blog. “To alleviate the problem, this NDK still provides the 4.2.1 binaries, which can optionally be used to build your machine code.” Turner adds that this release is called simply “r3″ because it is not limited to a specific Android platform/API level, after some developers incorrectly assumed the previous 1.6_r1 was limited to Android 1.6.
For more on Android NDK r3:
- read this Android Developers Blog entry
Related articles:
IDC forecasts Android shipments will near 70 million by 2013
Android explodes into the consumer consciousness
Over half of Android developers dissatisfied with app profits
Copyright © 2010 IT Knowledge Hub | Advertise | Contact | Privacy Policy | Terms of Use | Register