Samsung C3510 Corby POP cool touchscreen phone
Samsung C3510 Corby POP has a 2.8 inch touchscreen with Smart unlock feature. also it's user interface is said to be Cartoon UI and it also a upcoming event. it has very good sound quality with DNSe (Digital Natural Sound Engine) technology and has a 3.5mm audio jack. the internal memory of this phone is 30MB and it supports up to 8GB memory cards. also this is a 2G phone and even no wi-fi.
also it's camera is poor, 1.3MP one. C3510 Corby POP has a built in FM radio and couple of social networking applications.
Philips D908 super touch phone from philips electronics
Philips D908 runs with Microsoft Windows Mobile 6.5 Professional OS. the internal memory of this phone is 256MB and it supports up to 32GB memory cards.
also Philips D908 has a 5MP camera which comes with a LED flash. the camera has Face detection and geo tagging features. in connectivity side, this phone supports 3.6MBP/s HSDPA, and has both wi-fi and bluetooth. it has a GPS receiver with A-GPS support. also Philips D908 comes with couple of pre installed applications like PDF viewer and Organizer.
Motorola XT701 another super mobile phone with HDMI
since it has a capacitive touchscreen, XT701 supports multi-touch. also this phone has an Accelerometer sensor and 3.5mm audio jack.
in connectivity side,Motorola XT701 supports super fast 10.2MBP/s HSDPA connectivity and 5.76MBP/s HSUPA connectivity. also it has both bluetooth and wi-fi. the main camera of this phone is 5MP and it supports high quality video recording. the camera comes with xenon flash and supports Geo-tagging feature.
Motorola XT701 has a great feature which is rarely can see in new mobile phones. that is it's built in HDMI slot. it allows HD video (720p) playback through the phone.
Google Nexus One most talked mobile phone unofficial review
Google Nexus One is a one of the most talked mobile phone. if you have visited famous gadget review sites in last few months, you may realize it. any way, i can tell you this is a one of the super mobile phone which HTC ever made. and also it's a Android phone.
this phone has a 3.7 inch AMOLED capacitive touchscreen. it hasn't announced yet but will be available at the beginning of the year 2010. it's a multi-touch mobile phone which has an Accelerometer sensor as well. the internal memory of this phone is said to be 512MB and it supports up to 32GB memory cards.
in connectivity side, Google Nexus One supports 7.2MBP/s HSDPA,wi-fi and bluetooth. also the main camera of this phone is 5MP which comes with a LED flash. and the camera supports 2560х1920 pixels resolution.
the another most important thing is it's processor. Google Nexus One has a 1GHz Qualcomm Snapdragon processor. it has a GPS receiver,FM radio,Digital compass and lot more other common features. another new feature is it's dedicated Noise cancellation microphone.
it was really difficult to find a picture of it.
Nokia 7230 very cool design phone
when i see this photos, i remember Palm pre phone. this is Nokia 7230 and it's a upcoming phone. this phone will be available at the beginning of the year 2001. it has very nice design with slider opening keypad. also Nokia 7230 is not a very high end phone. it has very necessary features only.
Nokia 7230 is a 3G phone which has a 2.4 inch display. it also has a 3.5mm audio jack and good sound quality. the internal memory of this phone is 45MB and it supports up to 16GB memory cards. also it comes with a 2GB memory card included.
Nokia 7230 has a 3.15 MP main camera which gives good quality images. it has a Stereo FM radio and many pre installed applications.
Sony Ericsson Hazel, another eco friendly phone
Sony Ericsson has a mobile phone series called green heart. green heart phones are made with eco friendly materials and has applications like CO2 calculator. actually this is a good step of Sony Ericsson to reduce future e waste.
Sony Ericsson Hazel is the newest phone of this series. it's a full featured phone and will be available at the middle of the year 2010. Sony Ericsson Hazel has a numeric keypad and has a touchscreen as well. it has a 2.6 inch colour display and Accelerometer sensor. this phone has a Walkman technology media player which gives very good music quality. also the internal memory of this phone is 319MB and supports up to 16GB memory cards.
Sony Ericsson Hazel is a 3G phone which supports 7.2MBP/s HSDPA. it also has both bluetooth and wi-fi. it has 5MP main camera which gives excellent picture quality. the maximum picture resolution is 2560х1920 pixels. this phone has a GPS receiver with Wisepilot navigation support. and it comes with lots of pre-installed internet and music applications.
Review: Fring Video Calls on iPhone 1st Gen.
Fring installation and registration on iPhone is pretty easy; the login process is much better than back in the hay days when I was trying to use my Nokia N95-3 to make 3G network test calls. You basically choose a username, password and provide a valid email address and off you go. The app is smart enough to save the login and password so you don't have to re-login each time you use the app. The next step is to login to your Skype account within Fring. Fring also offers the bridge to login to other IM/VOIP services, check out their website for all the details.
After setting up, my first couple of video test calls using a MacBook Pro did not work, I would only get audio portion of the communication; on my MacBook Pro, the video button was grayed out and can't be gauged (LED off). Then magically, on the 3rd try, it just worked; I was able to see the videos coming through and audio pretty clearly. Speaking of audio, I did find a small bug where pressing the speaker icon did not toggle between headset and speaker output... not sure this is a common bug or just from this particular first generation "pwnd" iPhone. I plugged in a stereo headphones w/ mic and worked pretty good, in fact, this is probably how I'd recommend using if you are on the road. I placed several test calls afterwards, some went through while others got a bit choppy (it would delay the video transmission upwards of 1 minute or sometimes just not engage; at times calls would also be refused even though it was accepted). The buggy conditions are not consistent to be reproduced. Through my own surmise, I am guessing it may have something to do with having to go through Skype via Fring server? Although this is an unverified thought. While this mobile experience hasn't been perfected, I must award some much deserved credit to the folks at Fring for once again, pushing their technology envelope to bring this to your iPhone.
The concept of having video conference on the call WITHOUT having to pay a hefty fee to telecom operator is a sexy thought. Think about your next business trip and as you are waiting at an airport lounge or coffee shop and see your loved ones via WiFi network on your smartphone (of course, if it supports transmission via 3G network is even sexier). Currently Fring supports video conference on iPhone and Symbian S60 (2-ways!); its just a matter of time before Android gets picked up and I'm sure this puts pressure at Skype or even Google Talk to start supporting this feature in native form. Very cool indeed!
Nokia 5235 full touch phone with good music features
After launching apple iphone, mobile phone trend was changed to manufacture full touch mobile phone. but Samsung and LG were pioneers of launching this type high end phones. and the world's largest mobile phone manufacturer were silent. also their most talked N97 was not succeeded as they wish because of the Samsung and LG phones. but even after a silent period, Now they tend to manufacture full touch phones. there were lot's of examples for this in last few months.
Nokia 5235 is one of the newest phone of this type. as they says this is a really good music phone. it has a 3.2 inches resistive touch screen. it has an Accelerometer sensor, Proximity sensor and handwriting recognition feature as well. Nokia 5235 has 70MB internal memory and supports up to 16GB memory cards.
Nokia 5235 is a 3G enabled phone which supports up to 3.6MBP/s HSDPA speed. it has bluetooth but wi-fi is not available. also the main camera is 2.0Mp and supports video recording. Nokia 5235 has a GPS receiver with nokia Maps touch edition. also it has stereo FM radio and many useful built-in applications.
Nokia 2710 Navigation Edition cheap phone
Nokia 2710 is another newest mobile phone which announced in 2009 december. it's a Navigation phone but has necessary features only. therefore is cheap. this kind of phone is very ideal for tourists if he can't find a GPS receiver in some country.
Nokia 2710 Navigation Edition is also a very good music phone. it has a 3.5mm audio jack and 64MB internal memory. also this phone comes with 2GB memory card and supports up to 16GB memory cards. also 3G is not available in this phone but it allows to connect to internet via EDGE.
Nokia 2710 has a 2MP camera with video record support. the good thing of this phone is you get Nokia Maps with lifetime navigation license when you buy it.
Review: Pelican 7060 LED Flashlight
LED flashlights are in demand because it tends to draw a more intense lighting and in most cases uses less energy than traditional bulbs. Top of the line LED modules combined with high capacity lithium batteries can produce some serious lighting that our law enforcement officers rely on.
When Pelican released their new 7060 LED flashlight, I thought I would get my hands on a unit and step up to the big league. My first impression with Pelican's 7060 is that it isn't as compact has I thought it would be. Standing next to my 2D Maglite shows that its about 1" shorter and obviously more skinny. Considered a tactical flashlight, it is composed of hard plastic with grenade grip. Pelican outfitted this flashlight was an astounding 130 Lumen of lighting power, much higher than most of their competitors on the market (usually between 80 to 90 Lumen). The 7060 comes pre-charged right out of the box and first thing I did was to turn it on, and boy this flashlight means business. I was so impressed by its lighting, I ran into my daughter's room and turned off the lights (while my wife is changing her diaper), pointed my 7060 towards to ceiling which illuminated the entire room. This little flashlight lit up the entire room! Amazing!
I immediately pulled out the 2D LED Maglite and 3D Maglite for a comparison test; as you can see from the pictures below, the Pelican 7060 is the brightest hands down. I know I'm comparing Apples to Oranges seeing that I'm not using a Surefire or Fenix, but I will hopefully be able to arrange one soon. In the mean while, I've found some serious reviews from candlepowerforums.com for similar comparison.
Pelican 7060 makes it a good choice for those not wanting to deal with buying batteries as it comes with a rechargeable lithium-ion battery and a docking station along with a belt holder. Basically, this model is ready for you right out of the box. The battery has a run time of about 1.5hr and takes about 4-5 hours to recharge. While Pelican offers a cool 2-way switch (one on the side and one towards the back), I would have liked to see a lower power output setting (ie. go down to 10-45-90 lumens and Strobe to allow the battery run time to go up to 5-10 hour range. Pelican recommends to replace the battery after 500 charge cycles and I believe the replacement battery costs about $40.
Overall, I am very impressed by Pelican 7060's lighting performance. It is a very solid flashlight and super bright. I can see why the LAPD would choose this flashlight for their officers to use. If anyone is in the market for a solid flashlight, I would highly recommend taking a closer look at this unit. BTW, at the time of writing, there are 26 reviews on Amazon.com ($101 Shipped) in total and all of them have 5-stars!
Please find some photos of lighting comparison below (Left: 7060, Mid: 2D LED Mag, Right: 3D Maglite)
Beaming off the ceiling:
Beaming off the wall:
Review: Pelican i1015, toughest iPhone Case of all!
I've reviewed a good number of iPhone cases on this blog, as far as for true protection, the Otterbox series have been the name of the game. But I think I've hit the motherload of all protection. The Pelican i1015 is a new case for your precious iPhone (also works with iPod Toch) and can withstand just about anything you can throw at it (or throw it at). To tell you how tough this case is, Pelican didn't even bother with packaging. The case comes by itself along with an aluminum carabiner clip attached, I think their marketing folks are brilliant for making two points at once: 1). it's a tough son-of-a-gun and 2). going green!
Lets get to the features: The i1015 case is virtually indestructible; it is crush proof, water resistant, shock and dust proof. Pelican warns you not to submerge the case in water. Pelican engineers has really put a serious case together for the most active iPhone/iPod user.
My first impression with the Pelican is amazement; this case is huge. It is sort of ironic to see such a huge case that turns your slick iPhone/iPod about 8 times its size. In Pelican's defense, they did toss in a compartment for headphone cord management. With your iPhone in this case, it reminds me of Zack Morris's 80's mobile and you can forget about fitting it in your pocket. One thing to point out is this is not intended to be used like a case for communication. The case has no external control to anything (volume, power button, touchscreen, data port or speaker); it was designed as a listening case (while shut) or to be used opened up (kinda reminds me of portable video game cases). There is a headphone jack for you to connect your headphones to it but unfortunately it doesn't support the microphone from your headphones. I think Pelican should have enabled that feature to make using the phone a bit more friendly.
Mr. Obvious will tell you that this case is definitely not for your average joes. Its really meant for professional grade outdoor activities. For those unfamiliar with Pelican, these guys are famous for their super tough storage solutions. This Pelican i1015 case certainly lives up to their name.
CoPilot Live Guided GPS App $19.99 Sale
Hello, Stack Overflow!
Over the past year, an Android presence has been growing on a relatively new technical Q&A web site called Stack Overflow. The site was designed specifically for programmers, with features like syntax highlighting, tagging, user reputation, and community editing. It's attracted a loyal software developer community, and developers continue to express great praise for this new tool. Well, the Android team has been listening...and we agree.
Today, I'm happy to announce that we're working with Stack Overflow to improve developer support, especially for developers new to Android. In essence, the Android tag on Stack Overflow will become an official Android app development Q&A medium. We encourage you to post your beginner-level technical questions there. It's also important to point out that we don't plan to change the android-developers group, so intermediate and expert users should still feel free to post there.
I think that this will be a great new resource for novice Android developers, and our team is really excited to participate in the growth of the Android developer community on Stack Overflow. I hope to see you all there!
Back and other hard keys: three stories
Android 2.0 introduces new behavior and support for handling hard keys such as BACK
and MENU
, including some special features to support the virtual hard keys that are appearing on recent devices such as Droid.
This article will give you three stories on these changes: from the most simple to the gory details. Pick the one you prefer.
Story 1: Making things easier for developers
If you were to survey the base applications in the Android platform, you would notice a fairly common pattern: add a little bit of magic to intercept the BACK
key and do something different. To do this right, the magic needs to look something like this:
@Override
public boolean onKeyDown(int keyCode, KeyEvent event) {
if (keyCode == KeyEvent.KEYCODE_BACK && event.getRepeatCount() == 0) {
// do something on back.
return true;
}
return super.onKeyDown(keyCode, event);
}
How to intercept the BACK key in an Activity is also one of the common questions we see developers ask, so as of 2.0 we have a new little API to make this more simple and easier to discover and get right:
@Override
public void onBackPressed() {
// do something on back.
return;
}
If this is all you care about doing, and you're not worried about supporting versions of the platform before 2.0, then you can stop here. Otherwise, read on.
Story 2: Embracing long press
One of the fairly late addition to the Android platform was the use of long press on hard keys to perform alternative actions. In 1.0 this was long press on HOME
for the recent apps switcher and long press on CALL for the voice dialer. In 1.1 we introduced long press on SEARCH
for voice search, and 1.5 introduced long press on MENU to force the soft keyboard to be displayed as a backwards compatibility feature for applications that were not yet IME-aware.
(As an aside: long press on MENU
was only intended for backwards compatibility, and thus has some perhaps surprising behavior in how strongly the soft keyboard stays up when it is used. This is not intended to be a standard way to access the soft keyboards, and all apps written today should have a more standard and visible way to bring up the IME if they need it.)
Unfortunately the evolution of this feature resulted in a less than optimal implementation: all of the long press detection was implemented in the client-side framework's default key handling code, using timed messages. This resulted in a lot of duplication of code and some behavior problems; since the actual event dispatching code had no concept of long presses and all timing for them was done on the main thread of the application, the application could be slow enough to not update within the long press timeout.
In Android 2.0 this all changes, with a real KeyEvent API and callback functions for long presses. These greatly simplify long press handling for applications, and allow them to interact correctly with the framework. For example: you can override Activity.onKeyLongPress()
to supply your own action for a long press on one of the hard keys, overriding the default action provided by the framework.
Perhaps most significant for developers is a corresponding change in the semantics of the BACK key. Previously the default key handling executed the action for this key when it was pressed, unlike the other hard keys. In 2.0 the BACK key is now execute on key up. However, for existing apps, the framework will continue to execute the action on key down for compatibility reasons. To enable the new behavior in your app you must set android:targetSdkVersion
in your manifest to 5 or greater.
Here is an example of code an Activity subclass can use to implement special actions for a long press and short press of the CALL
key:
@Override
public boolean onKeyLongPress(int keyCode, KeyEvent event) {
if (keyCode == KeyEvent.KEYCODE_CALL) {
// a long press of the call key.
// do our work, returning true to consume it. by
// returning true, the framework knows an action has
// been performed on the long press, so will set the
// canceled flag for the following up event.
return true;
}
return super.onKeyLongPress(keyCode, event);
}
@Override
public boolean onKeyUp(int keyCode, KeyEvent event) {
if (keyCode == KeyEvent.KEYCODE_CALL && event.isTracking()
&& !event.isCanceled()) {
// if the call key is being released, AND we are tracking
// it from an initial key down, AND it is not canceled,
// then handle it.
return true;
}
return super.onKeyUp(keyCode, event);
}
Note that the above code assumes we are implementing different behavior for a key that is normally processed by the framework. If you want to implement long presses for another key, you will also need to override onKeyDown to have the framework track it:
@Override
public boolean onKeyDown(int keyCode, KeyEvent event) {
if (keyCode == KeyEvent.KEYCODE_0) {
// this tells the framework to start tracking for
// a long press and eventual key up. it will only
// do so if this is the first down (not a repeat).
event.startTracking();
return true;
}
return super.onKeyDown(keyCode, event);
}
Story 3: Making a mess with virtual keys
Now we come to the story of our original motivation for all of these changes: support for virtual hard keys, as seen on the Droid and other upcoming devices. Instead of physical buttons, these devices have a touch sensor that extends outside of the visible screen, creating an area for the "hard" keys to live as touch sensitive areas. The low-level input system looks for touches on the screen in this area, and turns these into "virtual" hard key events as appropriate.
To applications these basically look like real hard keys, though the generated events will have a new FLAG_VIRTUAL_HARD_KEY bit set to identify them. Regardless of that flag, in nearly all cases an application can handle these "hard" key events in the same way it has always done for real hard keys.
However, these keys introduce some wrinkles in user interaction. Most important is that the keys exist on the same surface as the rest of the user interface, and they can be easily pressed with the same kind of touches. This can become an issue, for example, when the virtual keys are along the bottom of the screen: a common gesture is to swipe up the screen for scrolling, and it can be very easy to accidentally touch a virtual key at the bottom when doing this.
The solution for this in 2.0 is to introduce a concept of a "canceled" key event. We've already seen this in the previous story, where handling a long press would cancel the following up event. In a similar way, moving from a virtual key press on to the screen will cause the virtual key to be canceled when it goes up.
In fact the previous code already takes care of this — by checking isCanceled()
on the key up, canceled virtual keys and long presses will be ignored. There are also individual flags for these two cases, but they should rarely be used by applications and always with the understanding that in the future there may be more reasons for a key event to be canceled.
For existing application, where BACK key compatibility is turned on to execute the action on down, there is still the problem of accidentally detecting a back press when intending to perform a swipe. Though there is no solution for this except to update an application to specify it targets SDK version 5 or later, fortunately the back key is generally positioned on a far side of the virtual key area, so the user is much less likely to accidentally hit it than some of the other keys.
Writing an application that works well on pre-2.0 as well as 2.0 and later versions of the platform is also fairly easy for most common cases. For example, here is code that allows you to handle the back key in an activity correctly on all versions of the platform:
@Override
public boolean onKeyDown(int keyCode, KeyEvent event) {
if (android.os.Build.VERSION.SDK_INT < android.os.Build.VERSION_CODES.ECLAIR
&& keyCode == KeyEvent.KEYCODE_BACK
&& event.getRepeatCount() == 0) {
// Take care of calling this method on earlier versions of
// the platform where it doesn't exist.
onBackPressed();
}
return super.onKeyDown(keyCode, event);
}
@Override
public void onBackPressed() {
// This will be called either automatically for you on 2.0
// or later, or by the code above on earlier versions of the
// platform.
return;
}
For the hard core: correctly dispatching events
One final topic that is worth covering is how to correctly handle events in the raw dispatch functions such as onDispatchEvent()
or onPreIme()
. These require a little more care, since you can't rely on some of the help the framework provides when it calls the higher-level functions such as onKeyDown()
. The code below shows how you can intercept the dispatching of the BACK
key such that you correctly execute your action when it is release.
@Override
public boolean dispatchKeyEvent(KeyEvent event) {
if (event.getKeyCode() == KeyEvent.KEYCODE_BACK) {
if (event.getAction() == KeyEvent.ACTION_DOWN
&& event.getRepeatCount() == 0) {
// Tell the framework to start tracking this event.
getKeyDispatcherState().startTracking(event, this);
return true;
} else if (event.getAction() == KeyEvent.ACTION_UP) {
getKeyDispatcherState().handleUpEvent(event);
if (event.isTracking() && !event.isCanceled()) {
// DO BACK ACTION HERE
return true;
}
}
return super.dispatchKeyEvent(event);
} else {
return super.dispatchKeyEvent(event);
}
}
The call to getKeyDispatcherState()
returns an object that is used to track the current key state in your window. It is generally available on the View class, and an Activity can use any of its views to retrieve the object if needed.
New resources and sample code on developer.android.com
Hey Android developers—if you've visited the online Android SDK documentation recently, you may have noticed a few changes. That's right, there's a new Resources tab, which was designed to take some of the load off the Developer's Guide. We've moved a number of existing resources to the Resources tab, including tutorials, sample code, and FAQs. We've also formalized a few of our most popular developer blog posts into technical articles; watch for more of these to appear in the future.
In addition, we just released a new batch of sample code, available now as a ZIP file download on the samples index page. And we're working on updating the way in which we distribute official sample code; more on that some other time.
The new sample code includes:
- Multiple Resolutions: a simple example showing how to use resource directory qualifiers to support multiple screen configurations and Android SDK versions.
- Wiktionary and WiktionarySimple: sample applications that illustrate how to create an interactive home screen widget.
- Contact Manager: an example on using the new ContactsContract interface to query and manipulate a user's various accounts and contact providers.
- Bluetooth Chat: a fun little demo that allows two users to have a 1 on 1 chat over Bluetooth. It demonstrates how to discover devices, initiate a connection, and transfer data.
- API Demos > App > Activity > QuickContactsDemo: a demo showing how to use the
android.widget.QuickContactsBadge
class, new in Android 2.0. - API Demos > App > Activity > SetWallpaper: a demo showing how to use the new
android.app.WallpaperManager
class to allow users to change the system wallpaper. - API Demos > App > Text-To-Speech: a sample using Text-To-Speech (speech synthesis) to make your application talk.
- NotePad (now with Live Folders): this sample now includes code for creating Live Folders.
We hope these new samples can be a valuable resource for learning some of the newer features in Android 1.6 and 2.0. Let us know in the android-developers Google Group if you have any questions about these new samples or about the new Resources tab.
Thanks for tuning in, and 'til next time, happy coding!
Knowing is half the battle
As a developer, I often wonder which Android platforms my applications should support,especially as the number of Android-powered devices grows. Should my application only focus on the latest version of the platform or should it support older ones as well?
To help with this kind of decision, I am excited to announce the new
device dashboard. It provides information about deployed Android-powered devices that is helpful to developers as they build and update their apps. The dashboard provides the relative distribution of Android platform versions on devices running Android Market.
|
The above graph shows the relative number of Android devices that have accessed Android Market during the first 14 days of December 2009.
From a developer's perspective, there are a number of interesting points on this graph:
- At this point, there's little incentive to make sure a new application is
backward compatible with Android 1.0 and Android 1.1. - Close to 30% of the devices are running Android 1.5. To take advantage of this significant install base, you may consider support for Android 1.5.
- Starting with Android 1.6, devices can have different screen densities & sizes. There are several devices out there that fall in this category, so make sure to adapt your application to support different screen sizes and take advantage of devices with small, low density (e.g QVGA) and normal, high density (e.g. WVGA) screens. Note that Android Market will not list your application on small screen devices unless its manifest explicitly indicates support for "small" screen sizes. Make sure you properly configure the emulator and test your application on different screen sizes before uploading to Market.
- A new SDK for Android 2.0.1 was released two weeks ago. All Android 2.0 devices will be updated to 2.0.1 before the end of the year, so if your application uses features specific to Android 2.0, you are encouraged to update it to take advantage of the latest Android 2.0.1 API instead.
In summary, Android 1.5, 1.6, and 2.0.1 are the 3 versions of the platform that are deployed in volume. Our goal is to provide you with the tools and information to make it easy for you to target specific versions of the platform or all the versions that are deployed in volume.
We plan to update the dashboard regularly to reflect deployment of new Android platforms. We also plan to expand the dashboard to include other information like devices per screen size and so on.
Evidence - Spooks BBC1 - Did you watch?
Mobile Experience Interrupted: No Data up in the Mountains
The whole mobile experience was going so smoothly but was interrupted when data disappeared. At least I was able to make phone calls at the top of the mountain...
Mobile Commerce's Rapid Developement
Just before Cyber Monday this year, Usablenet successfully launched 8 more ecommerce clients onto their mobile platform solutions; it appears Usablenet seems to be the vendor of choice when it comes to a quick turnkey solution to generate mobile sales. At my full time work, I've been asked to help brainstorm a full on mobile strategy for the company as well as work with various projects to help bring our retail products more mobile friendly (ie. local listings, product feeds, etc...).
Just today, I received a news alert about a popular comparison shopping engine PriceGrabber just launched an iPhone application. I'd argue that most ecommerce vendors probably has a product feed sent to PriceGrabber from their online marketing initiative; an application like this will inevitable force an ecommerce vendor to participate the mobile game regardless if they want to or not. This means that if your visitor found your product via PriceGrabber mobile, they will likely click on that product link; what happens next will make or break your mobile user experience. A mobile commerce ready website will redirect that user to a page that is formatted nicely to an iPhones screensize while an ecommerce site w/o mobile support will force that user to render the full website onto a small screen. Since PriceGrabber by nature is a "comparison" shopping channel, you should either get with a mobile program or hope your competitors haven't gotten around to it. In the same fashion, Google has been pretty much porting all of its search related products onto mobile (natural search, maps/listings, product search, news, images, etc...). Same goes to the some of the more aggressive coupon/affiliate marketing folks who's brought their services to mobile for online marketers (see my review "Affiliate & Coupon Sites Invade Mobile Experience"
As we approach to an exciting new year, now is a good time for every marketer to start thinking about a tangible mobile strategy.
Come to Our Virtual Office Hours
Starting this week, we're going to be holding regular IRC office hours for Android app developers in the #android-dev channel on irc.freenode.net. Members of the Android team will be on hand to answer your technical questions. (Note that we will not be able to provide customer support for the phones themselves.)
We've arranged our office hours to accommodate as many different schedules as possible, for folks around the world. We will initially hold two sessions each week:
- 12/15/09 Tuesday, 9 a.m. to 10 a.m. PST
- 12/17/09, Thursday 5 p.m. to 6 p.m. PST
- 12/22/09, Tuesday 9 a.m. to 10 a.m. PST
- 01/06/10 Wednesday 9 a.m. to 10 a.m. PST
- 01/07/10 Thursday 5 p.m. to 6 p.m. PST
Check Wikipedia for a helpful list of IRC clients. Alternatively, you could use a web interface such as the one at freenode.net. We will try to answer as many as we can get through in the hour.
We hope to see you there!
Optimize your layouts
Writing user interface layouts for Android applications is easy, but it can sometimes be difficult to optimize them. Most often, heavy modifications made to existing XML layouts, like shuffling views around or changing the type of a container, lead to inefficiencies that go unnoticed.
$ layoutopt samples/
samples/compound.xml
7:23 The root-level <FrameLayout/> can be replaced with <merge/>
11:21 This LinearLayout layout or its FrameLayout parent is useless samples/simple.xml
7:7 The root-level <FrameLayout/> can be replaced with <merge/>
samples/too_deep.xml
-1:-1 This layout has too many nested layouts: 13 levels, it should have <= 10!
20:81 This LinearLayout layout or its LinearLayout parent is useless
24:79 This LinearLayout layout or its LinearLayout parent is useless
28:77 This LinearLayout layout or its LinearLayout parent is useless
32:75 This LinearLayout layout or its LinearLayout parent is useless
36:73 This LinearLayout layout or its LinearLayout parent is useless
40:71 This LinearLayout layout or its LinearLayout parent is useless
44:69 This LinearLayout layout or its LinearLayout parent is useless
48:67 This LinearLayout layout or its LinearLayout parent is useless
52:65 This LinearLayout layout or its LinearLayout parent is useless
56:63 This LinearLayout layout or its LinearLayout parent is useless
samples/too_many.xml
7:413 The root-level <FrameLayout/> can be replaced with <merge/>
-1:-1 This layout has too many views: 81 views, it should have <= 80! samples/useless.xml
7:19 The root-level <FrameLayout/> can be replaced with <merge/>
11:17 This LinearLayout layout or its FrameLayout parent is useless
layoutopt.bat
in the tools directory of the SDK and on the last line, replace %jarpath%
with -jar %jarpath%
.UK MTEB Mobile Forensics Conference 2010
Rain on my Parade | Rain on my Parade
Rain on my Parade | Rain on my Parade Rain on my Parade | Rain on my Parade Rain on my Parade | Rain on my Parade Rain on my Parade | Rain on my Parade
Have you watch the Rain on my Parade from the Glee Episode?
Read the article below from tv.popcrunch.com:
This is it… the Glee fall finale, episode 13 “Sectionals” – and then we sit tight until April! Watch the video clips for Rachel (Lea Michele) singing “Don’t Rain on My Parade,” by Barbra Streisand and the Glee cast singing Kelly Clarkson’s “My Life Would Suck Without You” in these video clips.
Watch the video now, just copy and paste the URL below to your address bar:
This is it… the Glee fall finale, episode 13 “Sectionals” – and then we sit tight until April! Watch the video clips for Rachel (Lea Michele) singing “Don’t Rain on My Parade,” by Barbra Streisand and the Glee cast singing Kelly Clarkson’s “My Life Would Suck Without You” in these video clips.
Thank you for watching! If you want to have a direct internet TV in your PC, just download the software at the link below, just copy and paste it to your address bar:
Android Developer Challenge 2 Winners
SweetDreams
SweetDreams is a revolutionary tool that will finally allow you to go to sleep without worrying about changing your phone settings in order to avoid unwelcome late night calls. You can even use those inactivity periods to save battery power as well, and of course forget about enabling WiFi, Bluetooth or ringtones volume every morning again. Thanks to SweetDreams activation filters all those settings will be automatically determined based on time, location and even other parameters such as sounds near the phone or movement!!! All of that is available for you in the same really easy to use application. Just set your filters and SweetDreams will do the job for you.
What the Doodle!?
'WTD!?' is a real-time online multiplayer game where one player tries to draw out a given phrase and others try to guess it. Features FFA and Team games, Global Highscores, Personal Face Doodles, integrated Voice Recognition and more! Real-time drawing!? Built for performance, you'll really see the magic at first doodle!
WaveSecure
WaveSecure is the an innovative security product that provides users with complete mobile device and data protection. It enables users to remotely lock down and track down lost phones, get a copy of their data securely backed up, and remotely wipe data of the phone to protect user privacy. WaveSecure has been selected by leading Global brands such as Nokia as their preferred choice of mobile security service for premium S60 users in India and is one of the highest revenue generating Value-Added-Service (VAS) with the lowest churn in SingTel. tenCube has been selected as one of the Top 100 Tech startups in Asia by Red Herring and one of six Asian Innovators by Wall Street Journal; WaveSecure has also received numerous industrial recognition including the Mobile Monday Peer Awards in Singapore and is nominated a finalist in GSMA’s Asia Mobile Awards 2009.
Complete list of winners can be seen at this link.
Overall, Congratulation to you all the winners!
and Congratulation to you all, who have studied and still been trying to understand How to create good application in Android.
Let's Study Together!
Samsung M5650 Lindy newest phone with multi touch
Samsung M5650 Lindy is another very new phone. Lindy is a girly name and yes the shape of this phone is very suitable for ladies. it has a 2.8 inch capacitive touchscreen which supports multi-touch. it has very good music quality because of the DNSe (Digital Natural Sound Engine) technology.
Samsung M5650 Lindy has 50MB internal memory and supports up to 8GB memory cards. it has 3G and supports 7.2 MBP/s HSDPA. also the main camera of this phone is 3.15 MP and supports video recording as well. Samsung M5650 Lindy comes with very cool applications. it has Social networking integration with live updates and Find Music recognition service as well.
Popular Posts
- 199 iphone wall paper
- Scanbuy Announces Addition to Its Board of Directors
- Millions of Names Available for .Co Open Registration
- YouTube Mobile 3G Enhancements & Java Beta Launchd.
- What a wonderful Second Life!
- Google Wave: First impressions
- Nokia N8 + Bluetooth Keyboard + Mouse
- Developers unhappy over Oracle Android suit
- Caribou Coffee to Use Cellfire for Mobile Coupon Offer
- Catching up: 8 random things about me