Profile cover photo
Profile photo
Aladin Q
* matters.
* matters.


Post is pinned.Post has attachment
Fresh update for Advanced Wear Visualizer!

A new mobile companion app, additional renderers, better performances, more bug fixes, and so on.
Add a comment...

Post has attachment
Troll Watch Face is the first most expensive Watch Face you can find, it might even cost more than your own Android Wear watch.

This is not a sequel of Void Watch Face.
Add a comment...

Post has attachment
Android Wear 5.1.1 update on LG G Watch R.
Android Wear 5.1.1 (LG G Watch R)
24 Photos - View album
Add a comment...

Post has attachment
Boot Watch Face transits from ambient mode to interactive mode like your (favorite) boot animation.

Performance matters (Thanks +Colt McAnlis for that), it was possible to reach 60 FPS even on a such tiny device as Android Wear is (proof on the left:, and there is still room to improve, or save more battery.
Add a comment...

Post has attachment
Digistyle Watch Face or a typical numeric representation of time and date with style, animations and many options.

#AndroidWear   #WatchFace   #YAWF  (Yet Another Watch Face)
Add a comment...

Post has attachment
Just started to play more seriously with the new Watch Face API on Android Wear.
Add a comment...

Post has attachment
Android Wear 5.0.1 already available for developers (emulator), check your Android SDK Manager.

What can we quickly notice?

Android Wear
Google Play services 6.5.90 (1610726-534)

In the default launcher, the 3 last apps or menu options we launched are now remembered and put on top of the list (see screenshots).

The Watch Face selection screen scrolls faster than before and got an additional Recent category. And depending on the Watch Face, you can directly access its settings via the selection screen. 

Android Wear 5.0.1 (emu)
6 Photos - View album
Add a comment...

Post has shared content
Just unleashed my first Chrome extension, Enhanced Developer Console, which lets you highlight the statistics change displayed on the main page of your Developer Console.

Statistics change will start to being reflected after the first time you will use this extension (you have to click its icon in the address/search bar which will be only be displayed when you are in front of the developer console).

I plan to keep it relatively simple, since the console is already doing more than a great job concerning the statistics but lacks of these little highlight features.
It might have few bugs and it is not yet fully polished (UNIX timestamp epoch is not very human readable ;-)).

Hope you will like it.

No permission requested.
Released under the terms of the MIT license.
Add a comment...

Android Wear device codename simply seems to be based on fish name.

Kudos to +Brian Gaid who started to establish a list (Asus ZenWatch is missing, though the rumor initially said it would be robin).

LG G Watch  (dory)

LG G Watch R (lenok)

Motorola Moto 360 (minnow)

Samsung Gear Live (sprat)

Sony Smartwatch 3 (tetra)

Asus ZenWatch (robin???)
Add a comment...

Post has attachment
Firstly, I would like to personally thanks, in this particular order:
• +Wayne Piekarski, Senior Developer Advocate at Google (focusing on Android, Wear, and Glass) and moderator of the Android Wear Developers community on G+, who reached out in less than half a day.
• +Derek Ross, writer for Phandroid and Android Enthusiast among many others passions, who showed compassion and did a simple but efficient post reshare creating many ripples.
• +François Simond alias supercurio, a french mobile engineer mainly known for his work on Project Voodoo and recently involved in mobile camera and display calibration, who took the time to wrote a pertinent post and chatted with me via Hangout. He clearly shows his interest in preventing these critical issues for any developer, in improving the transparency concerning the removal process and above all, in understanding.

Secondly, my thanks goes to everyone who wished me luck, +1 and re-shared my post. I cannot cite you all because I do not want to be accused of any spam (obvious reason), but I am sure you will recognize yourself.

Thirdly, a little recap including where I think I failed. It may sound a bit paranoid, but I have no precise idea of what went wrong. Thus, I tend to see it as a sum of factors which triggered the removal instead of one big factor alone.
better safe than sorry, right?

Nov 10, 2014 at 2:36 PM - Receipt of a mail entitled "Notification from Google Play"
This is a notification that your application, Reversi for Android Wear, with package ID, has been removed from the Google Play Store.
REASON FOR REMOVAL: Violation of the spam provisions of the Content Policy.
Your title and/or description attempts to impersonate or leverage another popular product without permission. Please remove all such references. Do not use irrelevant, misleading, or excessive keywords in apps descriptions, titles, or metadata.

First potential mistake might be in the title itself: "Reversi for Android Wear".
Quoting the brand guidelines, "[...]Android™ should have a trademark symbol the first time it appears in a creative.[...]". Additionally, there are no specific guidelines for "Android Wear" together, so it might be entirely forbidden.

Second mistake is in the description(s): "Reversi (sometimes known as Othello) is a classic strategy board game ported to Android Wear."
According to Wikipedia, Reversi is marketed by Pressman under the trade name Othello. Also, "to Android Wear" is not compliant with the guidelines, it could have been "for Android Wear" (think as a term referring to a platform) but again there are no specific guidelines on it, it might be forbidden. Moreover, I did not included the mention "Android is a trademark of Google Inc.".

We are now only at the second line of the description: "This game will only run on Android Wear, including non exhaustively:".
Again "Android Wear", no further explanations needed except the redundancy of the same word increases.
Below this line was a list of supported Android Wear devices (ASUS ZenWatch, LG G Watch, LG Watch R, etc...), it's probably too short to be considered as a keyword list (and was not intended as being
one) but excess of the word watch might have also increase the weight of one of these unknown factors.

I will skip two paragraphs ("features" and "how to use it") because I do not see anything problematic except few redundancies with the word "player" to the last line of the description:
If you are using Wear Mini Launcher, its drawer will not interfere at all. As expected, Wear Mini Launcher will be properly restored after you exit.
Here again, I am pretty sure I made a mistake in citing "Wear Mini Launcher" which is a popular launcher for Android Wear, this can clearly fall into "Impersonation or Deceptive Behavior" even if the developer of WML is aware of that line. It also appears after all that this is not really relevant to the description of the application.

I did not go to appeal for the removal of Reversi, but instead re-uploaded another version with a minimalist description "Reversi, the classic strategy board game at your wrist." and nothing more (maybe too minimalist to be relevant for describing properly the app).

However, I have around 7 applications for Android Wear and around one day after the removal of Reversi, I edited the description (sharing the same mistakes) of another app to add a troubleshooting part:
Wait 10 to 20 seconds after install in order to be able to select it via Start or your app drawer on your wearable.
If it is still not available, open the Android Wear app on your handheld and select Resync apps in the settings.
If it is still not showing in the list, uninstall and then install it again, and be sure to have free space available on your smartwatch.

Again and mainly, citing "Android Wear" app might have triggered something.

Additionally, I have few alerts on my developer console concerning two old "unpublished apps": _We have determined that your app uses a library or SDK (com.mobfox.sdk) that is in violation of the
Developer Program Policy. Please note that beginning Aug 1st, 2014 the Developer Program Policy requires all updates and new apps uploaded to be compliant with the advertising ID provision of the
Developer Program Policy. Apps in violation may be subject to permanent removal from the Store._
I should have fixed that but since they were unpublished I totally ignored them, and that might be another mistake which I am going to fix.

Nov 12, 2014 at 9:02 AM - Notification of Google Play Developer Account Suspension
REASON FOR TERMINATION: Multiple violations of the Content Policy and Developer Distribution Agreement as outlined in previous emails sent to the registered email address of your Publisher account.

Of course, I went to appeal. And quickly (less than two hours after I sent my appeal form) received that the the initial decision was confirmed and that my developer account will not be reinstating.

Later on, things changed again.

Now I would like to give few hints, and I also really hope something can be done to improve the removal process.

• First thing after receiving any removal notification is to calm down ("don't panic" or "don't go berzerk").
It is totally normal to be angry or feel something. But being too much emotional instead of rational will not help you when you will write your appeal form.
Same goes for any social post, be respectful and describe things clearly instead of only being aggressive.

• Do not give up so easily and do not harass everyone you know and everyone working at Google, that is probably counter-effective.
Read stories about your case and gather more information on how they succeeded to regain their account. I did not lost hope despite I estimated a really low probability to fix my issue.

• Try to prove your good faith by already being involved in one or more communities related to Android developers, and by being involved I do not mean only +1 posts and saying "wow, great" to official representatives but more by helping each others out without any distinction.

• Social pressure is also a lever, I am not famous at all and I do not know personally anyone close to the Play Store but this can help to shed a light on your issue.
However, this is also a matter of luck since it will not work if everyone is using this lever, it will not work for everyone and we certainly do not want a place crowded with people trying to get a large audience in order to solve their issue (this should be handled by the support).

• Do not be mad if this is happening to you but not your neighbors (we can see plenty of app which are not very compliant, and on purpose).
That is indeed unfair, but wishing that others fall with you will not really prevent your fall anyway. This is another story, in fact.

• Finally, as strict as it sounds, remember that if the Terms of Service are violated, Google can Terminate an account at any time, for any reason, with or without notice.

About improving the removal process and content policy enforcement, non exhaustively:

• Highlighting in red the non compliant paragraph, or even better anything which might trigger a removal.
This would be a great improvement to know more precisely what is problematic in a title/description of a submitted app, even better before publication.
Some might argue that this will help spammers and other evil actors to bypass the rules. But like in IT Security, it has now been proven that obscurantism is not a viable solution anymore.

• Following the highlighting: allowing the developer to not have to re-upload the application under a different packagename, which leads to many issues including losing ratings, losing users, paid customers will not like it, broken links on the internet, etc. 
Because even if we can appeal for a removal of an application, this is only if we believe the process made a mistake. For instance, it is impossible to access its description in order to fix it:
"This particular app has been disabled as a policy strike. If your developer account is still in good standing, you may revise and upload a policy compliant version of this application as a new packagename."
This could be done by branching only one additional step, first having a chance to fix everything and update the problematic application, then if it is still not compliant, continue with the existing process flow (re-uploading a new version, policy compliant).

• Having a points system, like certain countries do with the driving license, so you can know if you are really close or not to lose your account. Being able to regain lost point at a slower rate will also mitigate the issue any developer could have in, let's say, more than 10 years.

• Providing more humans for developer support, as an example Google Checkout is extremely efficient for resolving issue or even answering questions.

• Having a tool, or something embedded in the developer console, to do a pre-check of the description probably internally based on what triggers a removal policy. This will/should not guaranty everything is compliant, but that will certainly help.

• Making a survey which ask Android Developers about how to improve this particular topic.

• A last note on being more careful with the fake ratings and reviews, and the reputation system:
We all know that some shady developers pay for having false ratings and reviews on their application, and I am glad the detection of this bad behavior has been improved across time.
However there is a major flaw, what will happen if someone pays for false ratings and reviews to be posted on its competitor and how can the competitor prove he is being framed and has nothing to do with all these suspicious ratings and reviews.

Important links

Brand Guidelines

Google Play Content Policy

Google Play Developer Distribution Agreement

Rating your application content for Google Play

App policy help guide

This post has already grown a lot, despite much more could be said. However I have to take care of my apps and will be a bit busy checking everything prior to republishing them.
Add a comment...
Wait while more posts are being loaded