Tag Archive 'j2me'


Aug 05 2008

Free Skype JavaME (J2ME) client for mobile device

Published by mac0002 under j2me

Great news for those who are using Skype to get connected with their contacts, now they can do so while on the move with the free Skype mobile client.

The mobile client offers chat feature as well as receiving calls from Skype contacts. However airtime charge may incur for receiving voice call, depending on the subscribers’ data plan.

The main advantage of this J2ME client is portability across a wide-range of mobile devices which implements MIDP 2.0. Although the Skype Mobile website lists only handful of supported device, in reality Mobile Skype is supported on a lot more devices.

Disadvantages include its inability to send SMS to your contacts and the inability to make voice calls. However in my opinion, the free Mobile Skype does its best considering it is written for mobile devices with limited capabilities.

You can download Skype Mobile from this website : http://mobiledownload.skype.com/

Tips
With little creativity on java jad file, you can install Mobile Skype on any MIDP 2.0 supported device without much trouble

Bookmark this post : These icons link to social bookmarking sites where readers can share and discover new web pages.

  • co.mments
  • del.icio.us
  • digg
  • YahooMyWeb
  • DZone
  • StumbleUpon
  • Technorati

Tags: , , , , , , , , , ,

No responses yet

Aug 05 2008

Extending Flash Lite with J2ME

Published by mac0002 under j2me

Felipe is one of the most diligent and active guys in Flash Lite community with great open source projects; such as Flyer Framework and Jarpa. Check out his post telling how he created a simple application where he extended Flash Lite with J2ME.

I’m proud to share a short application snippet of the next Jarpa Framework. Jarpa Framework wants to provide developers with the combined power of Adobe’s Flash Lite and Java’s programming capabilities.

Although I am sure he is making wonders in order to overcome OEM limitations; but apparently there are some ways. We are excitingly following these projects; and as soon as have some J2ME competency, will definitely contribute.

Great work!

Trackback URI | Comments RSS

One Response to “ Extending Flash Lite with J2ME ”

  1. # 1 hekim group Says:
    May 21st, 2008 at 12:48 We are excitingly following these projects is perfect.. thank you.

No responses yet

Aug 05 2008

J2ME GPS: Network on Wheels — Java Developers, Start Your Programming Engines!

Published by mac0002 under technology

When someone mentions the hottest new mobile, Internet-enabled, multimedia computational system, what comes to mind is the latest handheld, cell phone, or PDA device. But in the n Continue Reading »

No responses yet

Aug 05 2008

Raising interest in J2ME

Published by mac0002 under technology

Consider these facts:

– There are 708 million J2ME based phones as compared to 700 million PC based Java deployments.

– The market for commercial mobile applications is set to reach $1.6 billion by 2008.

– There will be an estimated 1.0 billion mobile phones in the world by end 2006.

I presented these facts in my Introduction to Mobile Java presentation last night to the Australian Computer Society Special Interest Group. The numbers are awe inspiring. The audience was bewildered when I told them that there is not a single company in Brisbane (Australia) that specializes in developing applications for this market.

The latest Javalobby newsletter bemoans the same fact.

“At JavaOne it was crystal clear that mobile vendors are eager to get more Java developers involved, but the mobile space still seems to be struggling for attention.”

So why is it struggling for attention?

First, lack of information. Java developers don’t realize that J2ME has grown at a rapid pace and that they can do more with it than they thought possible.

Second, lack of a ‘killer’ J2ME application. Ok, there are some good ideas in the market, but there is no application that catches the attention of the public.

Third, the respect factor. Developers don’t want to be seen working for a technology which is considered too simplistic and which is primarily written to develop games. From developing a J2EE app to J2ME MIDlets is considered a step down. Developers don’t realize that they can leverage their knowledge of J2EE to develop server centric J2ME apps.

Fourth, fear of competing technologies. What happens if J2ME doesn’t actually catch on? What happens if device manufacturers stop bundling J2ME and other technologies become more prevalent?

It will only take one well thought, commercially successful, mainstream application that will help lift the J2ME market. I am sure that the day is not too far.

Watch this space.

 

www.pass4side

No responses yet

Aug 05 2008

j2me

Published by mac0002 under technology

Contents:

 

Java ME Platform Overview

 
Java ME technology was originally created in order to deal with the constraints associated with building applications for small devices. For this purpose Sun defined the basics for Java ME technology to fit such a limited environment and make it possible to create Java applications running on small devices with limited memory, display and power capacity.

Java ME platform is a collection of technologies and specifications that can be combined to construct a complete Java runtime environment specifically to fit the requirements of a particular device or market. This offers a flexibility and co-existence for all the players in the eco-system to seamlessly cooperate to offer the most appealing experience for the end-user.

The Java ME technology is based on three elements;

  • a configuration provides the most basic set of libraries and virtual machine capabilities for a broad range of devices,
  • a profile is a set of APIs that support a narrower range of devices, and
  • an optional package is a set of technology-specific APIs.

Over time the Java ME platform has been divided into two base configurations, one to fit small mobile devices and one to be targeted towards more capable mobile devices like smart-phones and set top boxes.

The configuration for small devices is called the Connected Limited Device Configuration (CLDC) and the more capable configuration is called the Connected Device Profile (CDC).

The figure below represents an overview of the components of Java ME technology and how it relates to the other Java Technologies.

The Java Platform
Java ME Components
 

Configuration for Small Devices - The Connected Limited Device Configuration (CLDC)

 

Wireless Platform
 
The configuration targeting resource-constraint devices like mobile phones is called the Connected Limited Device Configuration (CLDC). It is specifically designed to meet the needs for a Java platform to run on devices with limited memory, processing power and graphical capabilities. On top of the different configurations Java ME platform also specifies a number of profiles defining a set of higher-level APIs that further define the application. A widely adopted example is to combine the CLDC with the Mobile Information Device Profile (MIDP) to provide a complete Java application environment for mobile phones and other devices with similar capabilities.

With the configuration and profiles the actual application then resides, using the different available APIs in the profile. For a CLDC and MIDP environment, which is typically what most mobile devices today are implemented with, a MIDlet is then created. A MIDlet is the application created by a Java ME software developer, such as a game, a business application or other mobile features. These MIDlets can be written once and run on every available device conforming with the specifications for Java ME technology. The MIDlet can reside on a repository somewhere in the ecosystem and the end user can search for a specific type of application and having it downloaded over the air to his/her device.

To learn more about CLDC please visit java.sun.com/products/cldc/index.html.

Configuration for More Capable Devices and SmartPhones - The Connected Device Configuration (CDC)

 

Digital Media Platform
 
The configuration targeted larger devices with more capacity and with a network-connection, like high-end personal digital assistants, and set-top boxes, is called the Connected Device Profile (CDC). The goals of the CDC configuration is to leverage technology skills and developer tools based on the Java Platform Standard Edition (SE), and to support the feature sets of a broad range of connected devices while fitting within their resource constraints.

Looking at the benefits the CDC configuration brings to the different groups in the value-chain the following can be said:

  • Enterprises benefit from using network-based applications that extend the reach of business logic to mobile customers, partners and workers.
  • Users will benefit from the compatibility and security of Java technology.
  • Developers benefit from the safety and productivity of the Java programming language and the rich APIs in the Java platform.

On the CDC configuration there are three different defined profiles:

  • The Foundation Profile (JSR 219)
  • The Personal Basis Profile (JSR 217) and
  • The Personal Profile (JSR 216)

For each of these profiles there are in turn a set of optional packages on which the actual application runs. To learn more about CDC please visit java.sun.com/technology/cdc/.

Java ME Platform for Converged Services

 
The Java ME platform covers everything from small limited devices with intermittent network connection to capable on-line mobile devices. The platform’s design enables it to flexibly and efficiently support the need for services covering all mobility channels. Services are easily portable between different configurations and profiles, and the same service can be delivered via different channels.

Developer Platform for Converged Services
 

Back to top

One response so far