Anfish is an open source project with the purpose to provide you with interesting stats related to your Android device. You can see the popularity of different Android OS versions, as well as the percentage of Android devices that are rooted. You can also see what devices and network operators are popular, and you can get stats by country or worldwide presented in neat pie charts.

In addition to the statistics data, Anfish also provides detailed information about your smartphone’s type of ROM, CPU, storage, camera and sensors among other things. Download Anfish on Google Play and let us know if you like it as much as we do!

More information

• Download Anfish on Google Play.
• Check out the Anfish open source project site.
• Visit AZSoft Technology Inc.

As the use of mobile apps becomes a daily part of life, more attention is being paid to how apps collect and use personal data. While some governments have yet to pass laws that require developers to fully disclose when apps collect and transmit data, the State of California has already taken steps to protect app users and will be working with a number of major tech companies to strengthen privacy protection for global app consumers. According to their recent announcement, six of the leading mobile application platforms (including Google) signed an agreement to foster innovation in privacy protection, promote transparency, and facilitate compliance with mobile privacy laws, including the California Online Privacy Protection Act (OPPA).

California mobile app privacy laws

Along with OPPA, mobile app users in California are further protected under California’s Unfair Competition Law or False Advertising Law. Under these regulations, any app that collect personal data from a California resident is required to have a privacy policy that states what information is collected and what that information is used for.  Any app that doesn’t adhere to these standards is subject to prosecution. The act has a very broad scope, so whether you’re a developer based out of Korea, Sweden, or Israel, as long as you have someone accessing your app in California, the same rules apply to you. A California resident can simply file a complaint with the Attorney General or take personal legal action through a private attorney.

Only collect the user data that you need

Assuming that you’ve informed your app users and have their permission, what kind of information should you collect? It should be just the basics, and even then, only the information that you really need. If you have a GPS or navigation-based app, of course it makes sense that you’ll need to location details, but it’s not necessary to have access to users’ contacts list. And if you’ve developed something as basic as a flashlight app, you probably don’t need to collect any information at all.

Protect collected and transmitted user data!

If it’s absolutely necessary to collect and transmit data, you need to ensure that the collected data is handled safely. Employ proper file permissions. Encrypt the locally stored data before sending it to the server to help protect the user’s confidential information. When communicating with a server over HTTP, avoid encoding user information in a URL that is used with HTTP. Instead, post it in a message body. Putting information in the URL increased the chances that it will be automatically logged.

Android Developers Blog – Best practices for handling Android user data.

More best practices for handling Android user data

We also would like to share some valuable hints on how to manage Android user data from Nick Kralevich, an engineer with the Android Security Team. In his article, Nick provides several key points to consider when developing your Android applications:

• Maintain a privacy policy – Trustworthy applications are up-front about the data they collect and the reasons for collecting it. Users are generally happy to share information via such apps if they believe they will personally benefit. A clear and concise privacy policy, with details about the type of information collected and how it’s used, goes a long way towards generating trust and good will.
• Minimise permissions – Android is unique among mobile operating systems for its simple, straightforward, operating-system-enforced permission model. All Android applications must declare the permissions they require, and users must approve these permissions before the application is installed. Users tend to distrust applications that require excessive permissions.
• Give your users a choice regarding data collection – Users are often happy to share their information, but they want control over that sharing. Trustworthy applications give users control over their information. For example, the Android Browser has privacy settings which enable users to control how their information is shared.
• Don’t collect unnecessary information – Trustworthy applications limit the kinds of data they collect. Collecting unnecessary information, especially if you never use it, just invites suspicion. When in doubt, don’t collect it.
• Don’t send data off the device – If you have to handle user data, ensure that the data remains on the device whenever possible. Users are comforted knowing that their private information strictly resides in the phone. Sending data outside the phone, even if done for the user’s benefit, tends to draw suspicion.
• … but if you have to, use encryption and data minimization – Sometimes, the collection of data is necessary. In that case, applications need to ensure that it is handled safely. A privacy policy will avoid leading to surprised and irritated users; in some cases, it may be advisable to prompt the user before transmitting data off-device.
• Don’t use code you don’t understand – In the open-source Android environment, it’s common (and good) practice to rely heavily on other people’s code, in the form of libraries and frameworks. But if that code is handling your users’ information inappropriately, it’s your problem. So make a point of checking code before you rely on it.
• Don’t log device or user specific information – Application developers should be careful about on-device logs. Android makes it easy to write to the phone’s log, and anyone who has looked at “logcat” output knows that it is full of important but seemingly random debugging information from many applications. In Android, logs are a shared resource, and are available to an application with the READ_LOGS permission (only with user consent, of course!). Even though the phone log data is temporary and erased on reboot, inappropriate logging of user information could inadvertently leak user data to other applications.

***

When you create a mobile app, it’s usually with the best intentions for your users – you want them to enjoy your game, save some time or money with a handy app, and spread its popularity among friends. At the same time, your users are putting their trust in your app by agreeing to your apps permissions, which includes disclosing personal data. Though you might not have any app users in California, it’s still best practice to your let your users know if you are collecting any information. Keep that trustworthiness going by ensuring your app only collects that data it needs, and make sure you keep that user data secure – your users will truly appreciate it!

App developers and tech enthusiasts, so what do you say? Will you take any extra efforts because of these laws? Are you considering privacy issues while downloading new apps? Make your voice heard!

More information

• Find out about California’s Online Privacy Protection Act (OPPA).
• Read Nick Kravelich’s article on best practices for handling Android user data.
• Learn more about using security and permissions in Android development.
• Get a general overview on Android Security at the Android Open Source Project.

Read more after the jump.

Over the past few months, we’ve been giving you some important information and tools to help you learn about Timescape™ extensions, including articles on how to develop Timescape™ extensions and use the Extension Development Kit, along with special sections on Developer Word dedicated to Timescape extensions and the Extension Development Kit (EDK). In case you missed all of this, you will get a new chance now as Robert Helmbro will guide you in how to create your very own Timescape™ extension – an excellent way to get visibility in Sony Ericsson phones. 

Starting with the 2011 Xperia™ phones and the updated software on the Xperia™ X10, you’ll be able to develop your own extensions for the Timescape™ application, Sony Ericsson’s unique feature that displays Facebook™, Twitter™, text messages, e-mails and alerts from your contacts as a flowing column on the home screen. And to help you develop your own Timescape™ app extension, we’ve got the Extension Development Kit (EDK) that includes all the necessary tools and documentation.

Robert Helmbro, Software Engineer at Sony Ericsson

If you already have a bit of Android™ development knowledge, you’ll find it fairly easy to create your own Timescape™ extensions. If you’re still a bit new to Android™ development, no worries, just familiarise yourself first with the Android development documentation mentioned below.

What is a Timescape™ extension?

For those of you who are new to the Timescape™ world, a Timescape™ extension is an Android™ application that provides Timescape™ connected UIs with content through a specified API.

The API is called Event Stream API, which can be thought of as a database of time-centric content. The extensions put content into the database. Then the visualisation application, such as the Timescape™ application, Infinite view or Timescape™-widget, presents the content to the user in an integrated way.

Prerequisites for creating a Timescape™ extension

You should have basic knowledge about Android™ application development. Such things as intents, broadcast events and content providers are central concepts in extension development. It is also assumed that Eclipse with the Android development tools (ADT) plug-in is up and running.

Documentation and sample code

Now, let’s get to the heart of this tutorial. First, download some documentation and code examples. This is, and more information about it, is available from the EDK developer section on Developer World. Download the Timescape™ code examples and documentation to get started. Once you’ve extracted the zip file, you’ll find the following content:

• RSSExtension – A sample extension with some attached documentation, intended for RSS type of extensions.
• SocialNetworkSample – A sample extension with some attached documentation. This sample is made to give an example of how a social network example can be made.
• SampleExtension – A sample extension with some attached documentation.
• EventStream_API.zip – Javadocs for the Event Stream API.
• Introduction_Timescape_extensions.pdf – Contains some basic information.
• SEMC_Xperia_Events_overview.pdf – Documentation about the visualisation application Xperia™ Events.
• Timescape_icon_design_guideline.pdf – Guidelines about icons needed in an extension.

A good starting point is to read the Javadoc for the Event Stream API. Extract the EventStream_API.zip. Go to the EventStream_API folder and open the index.html file in your favourite browser. Read carefully about the EventStream class. This will give you a good overview of how Timescape™ extensions work.

Downloading the Extension Development Kit

You are now probably excited for some hands on programming. Maybe you’re ready to look at the sample extensions and start modifying the code to try out your ideas, but hang on a little while longer.

As mentioned before, Sony Ericsson has created the Extension Development Kit (EDK) that can be used while developing extensions. The EDK consists of an emulator add-on containing, among other things, the Event Stream API and two visualization applications – Xperia™ Events and Infinite view. You can find out more about these applications later in the text. To install the EDK and create an Android Virtual Device (AVD), follow the “Installing the EDK” instructions on the EDK developer section.

You should now be able to start an emulator with your newly created configuration (AVD) by following the steps below:

1. In Eclipse, press Window > Android SDK and AVD Manager.
2. Select your new AVD and press Start.
3. Wait for the emulator to boot up and then scroll the main menu and you will find the application Xperia™ Events.

Xperia™ Events is a tool for testing Timescape™ extensions. Events are shown in a similar way as they will be shown on a real device. Now launch Xperia™ Events. You will only see an almost empty screen, since there are no extensions installed yet.

 Using the Social network sample extension

In order to fill Xperia™ Events with some content, let’s try out the Social network sample extension.

1. Browse to the SocialNetworkSample folder from EdkSnsSampleApp1.zip.
2. Create an Android project in Eclipse: File > New > Project… > Android > Android Project.
3. Set the ‘Create project from existing source’ checkbox and navigate to your recently extracted folder containing SocialNetworkSample.
4. Check EDK 1.1 as Build Target and press Finish.
5. Install the SocialNetworkSample to the emulator by right clicking the newly created project and press Run As > Android Application.

Now launch Xperia™ Events in the emulator again. A new tab should be present. Follow these steps: 

1. Press the new tab and then press Add account.
2. Press ‘SNS Sample extension – Register your account information’. Enter any user name and password you like and press Sign In.
3. Press back to see the dummy stream of events generated by the extension.

Try to press an event to see the detail view of it. At the bottom of the screen, it is possible to scroll all data in the database for this event entry. This is really useful when developing extensions. Also try to press the Infinite icon at the top right corner. What you should see now is the Infinite view. Infinite view is the detailed view of a contact. This shows everything related to the selected contact collected. For example, your extension gets its own tab with all events from the current friend.

Time for coding

Similar procedures could be done with the RSSExtension and SampleExtension. Some documentation is attached to all sample extensions. If you would like to create your own extension by modifying one of the sample extensions, I would recommend selecting the RSSExtension since it is most complete.

Hopefully, this has given you enough information for you to start a prototype of your own extension. When you’re ready, download the EDK and give it a go. If you have any questions, just post them in the EDK thread on Google groups, which we will monitor and get back with answers as soon as possible. Happy coding!

More information

• Learn more about Timescape extensions.
• Download the Sony Ericsson EDK.
• Download the Timescape™ extensions code example & documentation kit.
• Get an overview of the Sony Ericsson EDK.
• Ask a question though the EDK thread on Google groups
• Check out the EDK Frequently Asked Questions.
• Read more about Android application development.

Have you developed a killer game or app, but need help getting it off the ground? Don’t let your game or app languish in obscurity – get it in front of the crowd! Karl-Johan Dahlström, Head of Developer Relations at Sony Ericsson, can show you how at the upcoming AnDevCon in Silicon Valley, California.

About the session

Led by Karl-Johan Dahlström, the session Get Rich or Die Tryin’ – Building Success with Xperia™ PLAY is designed to show Android™ developers how to get promotion, top placement and increased revenues through Sony Ericsson’s marketing efforts.

– I hope a lot of people will get some valuable inspiration and thoughtful facts from this session, Karl-Johan says. I’m going to showcase how game developers can stand out with Xperia™ PLAY. Also, I’ll share some remarkable statistics that I hope will inspire developers to new levels of business success.

Sleepy Jack gameplay on the Xperia PLAY

Nate Smith, CEO of SilverTree Media, will join Karl-Johan on stage and share how his independent game development company has been able optimise, launch and maximise revenues with their latest title, Sleepy Jack, on Xperia™ PLAY.

The session takes place on Wednesday, November 9, 2011 from 2:15 PM – 3:15 PM. If you haven’t registered for the event yet, as a bonus for our readers, you can use the code sonyericsson to save $200 US off a 3 day conference pass.

About the event 

What can developers expect to get out of AnDevCon? Alan Zeichick, conference chair of AnDevCon II, says, “Developers can look forward to learning in an incredible environment that’s 100% focused on Android. With more than 80 hands-on workshops and technical sessions taught by everyone from Google engineers to independent app developers to representatives of carriers and handset manufacturers, AnDevCon II covers every inch of ground.”

The Sony Ericsson team will be in full force at AnDevCon. Come to our booth (#902) on the exhibition floor to book some face time with one of our Business Development Manager, or if you have technical questions, speak to anyone in our Developer Support group. In addition to the speaker session, check out our booth to demo all the latest Xperia™ smartphones, and try out Sleepy Jack and all our latest games available for Xperia™ PLAY.

BZ Media’s AnDevCon™ II, November 6-9, 2011, in Burlingame, Calif., is the independent conference for software developers building applications for Android smartphones, tablets and other devices. Learn more at http://www.andevcon.com/, or follow on Twitter @AnDevCon. 

More information

• Read more about AnDevCon on our Developer World Event Calendar.
• Get signed up on the AnDevCon Registration Page to attend this exclusive Android event.
• Learn more about the benefits of the Stand out from the Crowd program.
• Find out all about the Xperia™ PLAY Android mobile phone.

Anupam Nath

Back at Google I/O, Google had announced plans to add several capabilities to help developers manage their products more effectively on Android Market™. In particular, a very helpful publishing option – multiple APK support – is now available. With multiple APK support, you can have different versions of an APK file under the same product listing. The APKs file versions are completely independent APKs that share the same product name, but contain code and resources targeted for your particular set of customers. 

This feature also resolves some of the questions and comments we frequently get from developers, such as:

• Can we use an SDK lower than 2.3 and still support Xperia™ PLAY (which runs on Android™ 2.3)?
• We want to create high graphics textures for Xperia™ PLAY but other devices don’t support it and we don’t want to upload a separate application on Android Market™. What should we do? 

The multiple APK support option helps you manage all the above tasks without uploading a separate application to Android Market™ with a different package name for Xperia™ PLAY, or other specific devices. Leverage this feature to support various devices (such as phones and tablets), Android platform versions, or screen sizes, all while keeping the application builds inside the same package and product name.

Setting up Multiple APKs 

If you’re new to publishing on Android Market™, I’d recommended first going over the Preparing to Publish checklist and publishing on Android Market page on the Android Developers reference site to understand what you need to do if you plan to publish your application. Also review the publishing concepts for Android Developers. Here you’ll find a good explanation on key concepts regarding how the Android Market publisher site works, including descriptions on active APKs, simple mode versus advanced mode and the difference between “publish” and “save”. Most importantly, this page explains exactly how multiple APKs work.

Once you’ve made the decision to use multiple APKs on Android Market™, take the following facts into consideration:

• You will have just one entry in Android Market™ for your application, and different devices might download a different APK.
• You maintain one set of product details (app description, icons, screenshots, etc.). This also means you cannot charge different prices for different APKs.
• All users see only one version of your application on Android Market™.
• If you publish different APKs for different versions of Android, then when a user’s device receives a system update that qualifies them for a different APK you’ve published, Android Market™ automatically updates the user’s application to the appropriate APK.

Publishing multiple APKs

Assuming you’ve already prepared your application for publishing (including signing and versioning your application), you should be ready to publish on Android Market.

To activate multiple APK in the Developer console for Android Market, ensure you have the following settings:

1. In the Product details tab of Edit Application screen, an Upload new APK window opens when you first begin uploading your software. Click the Choose file button to navigate to and select the APK file.

2. When your APK file is uploaded, click the Save button.

3. Go to the APK files tab of the Edit Application screen.

4. Click Switch to advanced mode.

5. Click the Upload APK button and select the additional versions of the APK file to add. Select the Activate link to activate the APK.

6. When you are finished adding all the versions of your APK files for your application, click the Publish button to publish the APK files to Android Market™, or click the Save button to save your files.

The description circled below indicates which devices running a particular version of Android (in this case, API level 10 or 8-10) will be able to download this APK. The information shown in the description is automatically extracted from the manifest file.

Let us know…

We hope you take full advantage of the publishing options that the multiple APK support feature provides. If you have any questions, let us know through the Comments link at the end of this post.

More information

• Learn about multiple APK support in detail on the Android Developers site.
• Review the Preparing to Publish checklist and publishing on Android Market page on the Android Developers site.
• Read about multiple APK support on the Android Developers Blog.
• Get familar with our Xperia^TM game developer recommendations.
• Check out all of our game developer tips and tutorials.

Read more about this important recommendation after the jump.

Background

As you are readying a build for your game, it’s important to keep application versioning in mind, as part of the upgrade and maintenance strategy for your application. Users will want specific information about the application version that is installed on their devices, as well as the upgrade versions that will be available for installations.

This is also important if your application is tied to other applications, such as a published suite of applications, since other applications may need to query your application for its version, to determine compatibility.  Finally, publishing services through which you will publish your application may also need to query your application to also determine compatibility and upgrade/downgrade relationships.

Special considerations

You can set the version in the application’s Android Manifest manifest file. The version should be updated in the Android Manifest file with every new APK update. The game and APK version should be appropriate to the release.

More information about Versioning your application can be found on the Android Developers website at http://developer.android.com/guide/publishing/versioning.html.

Example

Here’s an example manifest that shows the android:versionCode and android:versionName attributes in the manifest element.
<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="com.example.package.name"
android:versionCode="2"
android:versionName="1.1">
<application android:icon="@drawable/icon" android:label="@string/app_name">
...
</application>
</manifest>
In this example, note that android:versionCode value indicates that the current .apk contains the second release of the application code, which corresponds to a minor follow-on release, as shown by the android:versionName string.

The Android framework provides an API to let applications query the system for version information about your application. To obtain version information, applications use the getPackageInfo(java.lang.String, int) method of PackageManager.

 About the Game developer tips

The Xperia^TM game developer recommendations offers guidance in developing games for Xperia^TM devices such as Xperia^TM PLAY.  The tips in this series provide additional information about some of the significant recommendations in that document.  Each tip provides the following information:

• Background. This is a fuller description of the recommendation. It answers the questions “why should I follow this recommendation?” and “when or where should I follow this recommendation?”.
• Special considerations. This describes any special considerations, such as device-specific considerations or application type-specific considerations that pertain to the recommendation.
• Examples. This shows screen captures or code snippets that further illustrate or explain the recommendation.

More information

• Check out the full list of Xperia™ game developer recommendations.
• Read our third game developer tip on saving large APK files to the SD card.
• Read our fourth game developer tip on displaying game keys and buttons.
• Get additional guidance and tips in building high-quality games on the Xperia PLAY developer page.

Read more about the Playstation® Suite SDK after the jump.

The PlayStation® Suite SDK supports C# as the programming language, and can run programs developed in C# on virtual machines equipped on both PlayStation® Certified devices and PlayStation® Vita. This demonstrates a obvious benefit to using the SDK – you are supporting development for multiple devices, you are creating certified hardware, and you are utilizing libraries to create new content that is not just limited to the Xperia™ PLAY, but to the entire suite of PlayStation® Certified devices, instead of relying of several different SDKs.

Another benefit that Sony Computer Entertainment is providing through the PlayStation® Suite SDK is helping you to further expand your business opportunities (as a developer or a publisher) to Android™-based portable devices. Detailed information of the PlayStation® Suite SDK, including how to download, will be announced through a dedicated PlayStation® Suite section on Sony Computer Entertainment’s official website.

In addition, by this October, Sony Computer Entertainment plans to provide content and service for PlayStation® Certified devices through the PlayStation® Store on PlayStation® Network, starting with original PlayStation® One games.

More information

• Read the official Sony Computer Entertainment press release.
• Download the Xperia PLAY white paper for the technical specs.
• Read our Xperia PLAY developer tips, tutorial and recommendations on Sony Ericsson Developer World.

Check out all the pictures and key takeaways from VDC 2011 after the jump!

As a major sponsor, Sony Ericsson had their own Developer Lounge on the main floor to show off the latest titles for the Xperia™ PLAY. On both days, we held a competition to see who could get the highest score in Asphalt 6: Adrenaline. Several attendees spent hours trying to achieve a top score, and in the end, we awarded three Xperia™ PLAYs to the highest scoring winners at the end of both days.

Anupam Nath from Sony Ericsson presenting at the session "Learn how to standout with Xperia PLAY" at VDC 2011.

From Sony Ericsson, Aaron Duke and Anupam Nath hosted a speaker session called “Stand out from the crowd with Xperia™ PLAY”. Attendees received an explanation of the benefits for developing for the Xperia PLAY, as well an overview of guidelines and recommendations for game developers. In the Q&A session that followed, Aaron and Anupam took lots of great developer questions from the crowd. Several developers asked about the games launcher, including whether or not Sony Ericsson takes a cut of the revenue (we do not!). In the end, we also handed out an Xperia™ PLAY to a lucky audience member – Kenneth Ng (pictured above in feature image). Thank you to everyone who visited our booth and attended our session. We look forward to seeing you at the next developer event.

Don’t forget to check our Picasa album with pictures from VDC!

Featured band "Cake" performs at VDC 2011.

Scott Tsumura.

How did you get started as a game developer?

In 1976, I started as a developer for arcade games and helped to bring several notable products to market, such as Moon Patrol and Kung-Fu Master. I also was responsible for bringing Japanese titles to the U.S. and conversely, introducing U.S.-made computer games to Japan, including Lode Runner. I attribute Lode Runner, a game that I encountered while temporarily working in the U.S., as the catalyst for moving here and driving my passion for gaming.

What first got you interested in mobile gaming, and what do you think the future of mobile gaming is?

Travelling back and forth from Japan for business, I was constantly carrying mobile phones, which at the time were very bulky and heavy and had no display for games. As mobile phones got smaller and cheaper, their popularity grew and mobile gaming began.  Today, smartphones have the screen resolution and processing power to play console games.  So, I believe the future of mobile gaming will be based on strong multiplayer experiences.

Can you tell us about your history with Lode Runner?

The original game, called Kong, was invented as a PC game by Doug Smith in 1982, and became published under the title Lode Runner. I was responsible for gathering a team of developers, and worked directly with Doug to publish several versions for Japan. In 1984, I helped developed the arcade version and numerous sequels, which marked the first-ever PC game to launch as an arcade version. At Tozai Games, I have continued to oversee the development of Lode Runner versions to other platforms. Now, I’m excited to be working closely with Southend Interactive to develop Lode Runner X for the Xperia™ PLAY.

How was the game ported from console to Android™ mobile?

We are working with Southend Interactive to build Lode Runner X. They used their own in-house game engine called the PBX. The engine provides support for a diversity of platforms including native Android, XBOX 360 and PS3. Utilizing this compatibility, they are able to transfer the gameplay logic without rewriting anything. Rendering, controls, sound playback and menus needed to be adapted for the PBX Android interfaces to complete the port. All assets needed to be updated as well. Texture resolutions and the level of detail of models needed to be decreased slightly, as well as changing texture and sound compression.

Are there any special features or new levels planned for Lode Runner X?

Lode Runner X for the Xperia™ PLAY will have the full journey mode and all the single player puzzles of the console version, including all of the environments and special features. But, the puzzles were so well received that we are considering adding some brand new puzzles to this version.

New level on Lode Runner X.

Do you have any final comments about developing Lode Runner X for the Xperia™ PLAY?

Developing to the Xperia™ PLAY doesn’t differ from developing to any other Android device. Sony Ericsson provides libraries and source code for utilizing the Xperia™ PLAY controller as well as how to display an Xperia™ PLAY compatible game in the Xperia™ PLAY Game Launcher. As the Xperia™ PLAY device is Android 2.3 enabled you also have the possibility to utilize the “Native Activity” library. This renders all Java code obsolete, making the games pure C++ code, which increases performance and simplifies the work flow.

We (at Tozai Games) are really pleased to be working with Sony Ericsson to bring Lode Runner X to this newest platform. The playability of the game on a mobile device with dedicated controls will be really exciting for a wide range of gamers. It’s a great opportunity to bring the most enjoyable gaming experience from console to mobile.

Thanks so much, Scott-san! Developer World appreciates your time.

And if there are other classic arcade games (Moon Patrol, R-Type or Kung Fu Master perhaps?) that you’d like to see for Xperia™ PLAY, let us know!

More information

• Read the official Lode Runner press release.
• Learn more about Tozai Games.
• Get more information about Southend Interactive.
• Download the Xperia PLAY white paper for the technical specs.
• Read our Xperia PLAY developer tips, tutorial and recommendations on Sony Ericsson Developer World.