Your Ad Here
Showing posts with label development. Show all posts
Showing posts with label development. Show all posts

Monday, July 12, 2010

Google announces Google App Inventor, a simple-to-use DIY app maker.

Today Google announced a simple-to-use DIY app maker called Google App Inventor.

Google App Inventor brings Android development to non-programmers, employing a design scheme that relies on visual blocks rather than writing pages of code, the App Inventor -- In true Google style, still in Beta, of course -- has functions for just about anything you can do with an Android handset, including access to GPS and phone functionality.

I can imagine this would be fantastic in classrooms.

more information here: http://appinventor.googlelabs.com/about/
complete this form to apply for access: https://services.google.com/fb/forms/appinventorinterest/







Thursday, October 29, 2009

Android 2.0 Platform Highlights


New User Features

Contacts and accounts
  • Multiple accounts can be added to a device for email and contact synchronization, including Exchange accounts. (Handset manufacturers can choose whether to include Exchange support in their devices.)
  • Developers can create sync adapters that provide synchronization with additional data sources.
  • Quick Contact for Android provides instant access to a contact's information and communication modes. For example, a user can tap a contact photo and select to call, SMS, or email the person. Other applications such as Email, Messaging, and Calendar can also reveal the Quick Contact widget when you touch a contact photo or status icon.

Email
  • Exchange support.
  • Combined inbox to browse email from multiple accounts in one page.

Messaging
  • Search functionality for all saved SMS and MMS messages.
  • Auto delete the oldest messages in a conversation when a defined limit is reached.

Camera
  • Built-in flash support
  • Digital zoom
  • Scene mode
  • White balance
  • Color effect
  • Macro focus

Android virtual keyboard
  • An improved keyboard layout to makes it easier to hit the correct characters and improve typing speed.
  • The framework's multi-touch support ensures that key presses aren't missed while typing rapidly with two fingers.
  • A smarter dictionary learns from word usage and automatically includes contact names as suggestions.




New Platform Technologies


Media Framework

Revamped graphics architecture for improved performance that enables better hardware acceleration.


Bluetooth
  • Bluetooth 2.1
  • New BT profiles: Object Push Profile (OPP) and Phone Book Access Profile (PBAP)

New Framework APIs
  • Android 2.0 includes several new developer APIs.

Thursday, September 17, 2009

Android 1.6 (Donut) SDK released, adds several new features



The developer kit for Android 1.6 is now available here. Android 1.6, also known as the Donut build, includes several new features and optimization tricks designed to greatly enhance the next version of Android. The SDK and the Android Developers blog have revealed some interesting previews of those features.


Quick Search


Android has universal search in Donut, which will scan all areas of a phone’s data – e-mail, SMS messages, and even third-party apps that are “searchable.” The system is able to recognize which results are most important to users, so contacts or apps that have been previously clicked will move to the top of future searches.


Improved Camera, Camcorder, Gallery


The Android Camera, Camcorder, and Gallery apps have been updated with an interface that makes it easier to navigate between each. Switching from camera to camcorder is easier, and the camera moves 39% faster than previous versions. There is also a 28% improvement in speed when taking one photo and moving along to next.


New Android Market


We knew this was coming but I bet you’re still happy to see there is a noticeable improvement. The Market has a new interface; options to pick between most popular paid apps, most popular free apps, and newest apps; screenshots if the app developer added them.


Text-to-speech engine

The multi-language/accent “Pico” will make Android speak text in English (American or British), French, Italian, German, and Spanish. From the description, I’d gather that this is better than the current TTS library previously seen on Android. G1 or Dream users will have to download the new engine once it is released.


Gestures

App developers can now take advantage of in-app gestures. Swipes in any direction would perform any function that the developer ties to those movements.

There is also a new Battery Usage Indicator, support for CDMA (Sprint and Verizon networks), expanded support for different screen resolutions and densities, and a new version of OpenCore with audio codecs.

Enjoy!

Tuesday, September 1, 2009

More Androids head towards Australian shores


A new breed of Androids is about to touch down in Australia as handset makers put the iPhone's dominance to the test with new smartphones built on Google's mobile operating system.

While HTC is the only company to have released Android handsets in Australia, Samsung will unveil its first Android offering next week with the launch of the Icon Galaxy.

The Galaxy taps into the desire to customise and personalise phones and integrate them with applications used elsewhere Tyler McGee, telecommunications vice-president at Samsung Australia, said.

"People are now buying their fifth, sixth or seventh handset, so I'd say, globally, the smartphone category is moving fast into the mainstream," he said.

The Galaxy has an organic LED screen and 5-mega-pixel camera, and 8GB of internal memory (which is upgradeable to 24GB) also helps to boost its smartphone credentials.

The launch of the Galaxy will be followed closely by HTC's Hero, which is due in Australia before October. No stranger to the Android platform, HTC launched the G1 Dream in Australia last February and its HTC Magic followed a few months later.

"We've certainly taken leadership with Android. We believe that in the next 18 months to two years that the cloud [where you store all your contacts and photos etc] will have a determinate factor on what devices you choose," Anthony Petts, HTC's regional sales and marketing director, said.

He said the Hero would offer better functionality and an improved user experience with a new capability, called "scenes", that allows users to group weekday or weekend usage profiles using widgets that are live and intuitive.

"We are continuing to expand the Android portfolio of products and strongly believe end users are looking for different sizes, form factors and keyboards, so we're giving them a variety of choices," he said.

While no other handset makers have formally announced new Android models for the Australian market, Motorola is reported to have two phones close to completion and set for release to some markets in September, although the company declined to provide specific timings.

"Motorola can confirm that we will be launching Android handsets but can't disclose any details at this time," it said.

Like the iPhone, one of Android's key selling features is the mass of third-party applications being created for the platform. The Android market now has 8000 applications for download and the fact that these can be built on open-source technology has made it a popular platform among developers.

Petts said Android applications delivered a unique level of depth, integrating tightly with functions such as cameras and maps, exemplified by the popular Sky Maps application, which can locate a position using the GPS to map out constellations visible from a particular location.

But interesting applications may not be enough to win over the mainstream smartphone market, Robin Simpson, a research director at Gartner, said.

"Success in the smartphone market is all about usablity and cool design. Google doesn't control the hardware so if phone makers don't come up with the good designs, that will make the platform less attractive."

Tuesday, June 30, 2009

Android developers get native-code kit


A native application development kit has been released for Android developers, offering a way to create certain kinds of high-performing applications for handsets running the Google platform.

Android applications run through the Dalvik virtual machine, which emulates a Java virtual machine. On Thursday, the Android Native Development Kit (NDK) was released, allowing coders to create parts of their Android 1.5 applications outside Dalvik, using native-code languages such as C and C++.

This approach would not ordinarily produce a massive performance boost, but it does allow developers to reuse existing C and C++ code for Android applications.

Android engineer David Turner wrote in a blog post that the NDK, which is an adjunct to the standard Android software development kit (SDK), could be used for writing higher-performing applications, but also had its drawbacks.

"Your application will be more complicated, have reduced compatibility, have no access to framework APIs, and be harder to debug," Turner wrote. "That said, some applications that have self-contained, CPU-intensive operations that don't allocate much memory may still benefit from increased performance and the ability to reuse existing code. Some examples are signal processing, intensive physics simulations, and some kinds of data processing."

Saturday, May 30, 2009

Android Developers Challenge 2 announced

Developers will submit their apps to one of 10 specially-designated ADC 2 categories (see below) beginning in August. An application can only be submitted to a single category.

First Round
In late August (final date to be announced), users of Android-powered handsets that can access the Android Market will be able to obtain a special ADC 2 judging application from the Android Market. With this app, they can download, test, and rank applications submitted to the challenge. Users choosing to participate in the review process will download submitted apps randomly and will rate them along a number of criteria, resulting in a final score for each app. The results from this first round will generate the top 20 applications in each of the 10 categories (200 apps total), which will go into the second round.

Second Round
The top 20 applications in each category will proceed to the second round. Android users will then be able to download the final applications and evaluate them in the same manner as during the First Round using the ADC 2 judging app. At the end of the voting period, applications in each category will be ranked, with the community vote constituting 45% of the final judging score.

Along with the public ranking, a team of Google-selected judges will evaluate the applications. Their scores will constitute 55% of the final score.

Eligibility

The ADC 2 contest is open only to applications that have not been published -- whether through Android market, a public web site, or any other means. An application that has already been made available to the public (at the time of judging) is ineligible, regardless whether it is free or sold commercially. Additionally, applications that were entered in the ADC 1 contest are ineligible for the ADC 2 contest, regardless whether they were winning apps. Similarly, updated versions of applications entered in the ADC 1 contest are ineligible for ADC 2.

When you enter an application in the ADC 2, we will make it available to all contest judges for free, exclusively for the purposes of judging. If you intend to sell your application after the conclusion of the contest, you may submit a "trial" version of the application for judging. We recommend that your trial version include full functionality, but with a timed expiration, rather than including limited functionality with no expiration. Judges will evaluate your application based only on the functionality accessible to them, so it makes sense to provide the fullest range of capabilities possible in your contest app.

Teams and business entities may enter applications in the contest, but each team or entity must designate a single developer entity who will be responsible for uploading the application. Should the application be selected as a contest winner, all payments will be sent to the developer entity only. Further division of funds is the responsibility of the team leader or business entity representative.

All submitted applications must run on Android 1.5 and be in English.

Categories

  • Education/Reference
  • Games: Casual/Puzzle
  • Games: Arcade/Action
  • Social Networking
  • Lifestyle
  • Productivity/Tools
  • Media
  • Entertainment
  • Travel
  • Misc

Awards

Prizes will be distributed as follows; all prizes are in USD:

For each of the 10 categories:

  • 1st prize: $100,000
  • 2nd prize: $50,000
  • 3rd prize: $25,000

Overall (across all categories)

  • 1st prize: $150,000 (meaning the overall winner will receive $250,000)
  • 2nd prize: $50,000 (meaning the 2nd prize winner will receive up to $150,000)
  • 3rd prize: $25,000 (meaning the 3rd prize winner will receive up to $125,000)

In addition, attendees of selected developer events will be provided with devices intended for use in developing submissions for ADC 2.

Timeline

Note: this timeline is subject to change until the Official Rules are published.

  • May 27 - Google I/O: ADC 2 announced
  • June: Full Terms and Conditions made available
  • Beginning in August: submission site opens, developers submit apps
  • Approximately 2 weeks later: submission site closes; ADC2 client/scoring app goes up on Market; users begin reviewing apps
  • Mid October: first-round judging ends
  • Mid November: final judging ends, winners announced


more details:
http://code.google.com/android/adc/

Saturday, February 7, 2009

2 quick tips on Database development on Android

[no, this is not really a pic of me]

I've been teaching myself development for the Android platform for a few months now, and I thought I'd share a couple of what I consider not-so-well documented requirements for setting up successful database applications on the platform.

These are solutions that I personally have found poorly documented for the beginner, and it took me some time to stumble upon them.

These are not written in stone, and I'm sure a more capable developer may have other ways of doing this, all comments/suggestions welcome!

Firstly, create your entire database schema with one 'create' statement.
I didn't find this easily documented as a requirement but this link on code.google.com spells it out nicely.

Secondly, when creating a database with multiple tables, incorporate the database name into your table create statements. Like this:

private static final String CREATE_ITEMS_TABLE =
" create table " + DATABASE_NAME +"." + ITEMS_TABLE +
" (_id integer primary key autoincrement," +
" title text not null);";

db.execSQL(CREATE_ITEMS_TABLE);


.. This took me a good while to realise, as your application will compile and work successfully for any transactions involving the first table, but not subsequent ones. You'll receive 'table not found' errors if you look in the debugger error messages.

I stumbled upon this via a diagram on the sqlite site:

.. more diagrams here for your reference.

Most of the examples available only use one table to demonstrate techniques, but as anyone who has been coding for more than a few months will know, all even slightly complex applications will require more.

Anyway, hope this has been useful to someone out there. If it has, please let me know.

And again, if I've got something wrong, please let me know... we're all in this together :).



till next time,
G
Your Ad Here

Search Me