Friday, November 5, 2010

Copied from The Google Help Fourms
Written by Rajseh S.

This ain't my job but I choose to post the major or most common unresolved issues with the android market here every month.
Shall keep updating this question or thread so that this thread is visible.
If the 'google guides' find this constructive, they might mark this thread as sticky for that month .. and provide answers here or in the respective threads.


Many posted on it are year old issues and still open. Posting again anyway. Few posted in Jan/.../Oct 2010 thread were fully fixed.


At least 2.2 aka FroYo users have these new features:
- update apps automatically, depending on permissions
- installation of apps to SD Card as long as the developer enables this
This is supposed to be ready but isn't yet released to the public yet:
- get/buy apps through web interface from a computer to install over internet automatically to your chosen android device. Expecting this to go public in a month or two.
In any case most are still on earlier (2.1) firmware .

-------- There is some 2k character limit on initial posts. (Erroneously claims to be 8K). Shall post the rest through an update --------
Updates:

1) Far too many have been having issues with app download/installation. This issue has been around since market started but in the recent past (~a month), this has gone to a different degree. Probably associated with the new market app that was silently updated or due to the server changes to accommodate paypal based payment ('welcomed'). In any case pathetic sub-beta performance.

2) Payment processing errors must not show up as download issues.
T-Mobile billing is good. Expanding to add more countries is good (but must be faster). Payment processing errors should not be so common and even when common, these must not show up as 'download issues' or affect downloads. Error reporting needs correction. And errors need to be avoided. (Again hoping the web interface will make things a little better)

3) Is downloading a file .. okay 1MB in size over Wi-Fi or 3G or even 2G/GPRS such a challenge? Almost every app hits some 'download error issue' and every user is unhappy with some developer for no mistake of theirs.
Yeah wireless connections might be flakey. If kids can code around ftp & bit-torrents for these, can't google - the giant fix this .. given one whole year?

4) Apps to SDCARD ... not all have 2.2/Froyo and this not being the default not many devs bother to use the tag explicitly.
5.a) Are unlocked devices expected to have full market access? Many do not have. Why not? We do see that copy protection is taking a shift from forward-locking to app specific license check (LVL). Anyway as of now even in countries supposedly allowing market access, many devices seem to suffer.
5.b) LVL must include package integrity check to rule out tampering at the platform level. This will ensure that tampered packages don't run on devices without mod_ed firmware (rooted). Obfuscation is a work-around only. Not a solution.

6) New firmware build loses full market access. While this too might change with LVL, it is a major issue today. More than once, when a operator/manufacturer OTA updates a new build, the market app falls apart. The server doesn't recognize the market client (app's fingerprint?) and would not serve 'copy-protected' apps. Isn't there a process between Google and those using google products like 'android market' app in their firmware? Is communicating the build key / fingerprint to provision in the market impossible because we are in stone age without Internet? May be.Why is provisioning the market, before everybody using a particular official firmware complains, an impossibility?
(Issues 5.a and 6 could are related in a few cases)
7) Why is the search giant finding it so tough to have an official website with all apps listed + searchable? Buying on web isn't essential but showcasing is.
Visibility is very very poor. And so is sale/distribution. I'll remove this entry when we get to see this working on market.android.com; we did see the beta in Google IO keynote.

8) Multiple things repeatedly requested by many .. these too do affect market experience:

11/1/10
a) Commenting system in market client must improve, developer must be able to reply to specific comments and/or contact users.
b) Backing up apps (and associated data) and one click sync and optional quick update is essential to have a smooth market use experience. (FroYo gets closer to the solution but isn't there yet)
c) Copy-protection ... licensing based on keys is a good step forward but could we have it around an open sourced market client and client-server API?
d) Google apps account must be usable with the market
e) Multiple versions of the same package must be allowed in the market as the SDKs are not backward compatible. Yeah reflection etc are cool but even Google doesn't have googles, navigation and other new apps for cupcake users. Certainly not a hardware constraint.
f) Allow deep links in app description for developers and please increase the word/char limit there. If fear of devs submitting keywords as long description is the issue, provide a details sub-section that you may not index on search at all.
g) the dev console should give better statistics (and may be an anonymous id to converse with commenters). Too bad to rely on third party websites even for deep statistics.
h) market API and checkout sale point API must be openly published for developers to gather information quickly.
i) adult content means different stuff to different people; provide ways to mark apps as suitable for 12+ and a filter in the client. a platform level global-lock would also be useful. In the current state, kids can't be allowed to play with the phone / market app. Allow crowd rating of app's adult content level along with general rating stars.
j) ask for a pin before allowing to buy an app. I want my young cousin to explore the device but talk to me before buying apps. (With enterprise additions for other apps in FroYo, market too should update to demand pin before purchase)
k) market does need to expand to many more countries for both buyers and sellers (This has been dead slow)
l) it must be possible to target specific devices and device features (sdkversion, screen-size and existing tags don't suffice) with the same app package in market (In this aspect we are getting closer but still gaps remain)
m) search history in market client app must be controlled (clearable) by user easily (in FroYo?)
n) In app purchases must not come through workarounds
o) Refund policies need attention. Developers are put in a very delicate situation here.
p) More filters and subsections have been requested by many in market client app
q) many would like to 'request an app' through market client (& web not the forum)
r) ability to instantly block all apps listed in the market from a particular developer account on individual phones and then flag so later for server to identify the rogue developer (not just a rogue app)
s) developers would like a way to gift an app ... not to bypass checkout and get paid elsewhere but to encourage testers, reviewers etc without having to ship unprotected apps by other means
t) would paypal bring in-app payment to android? Hope. And hope this is available through checkout itself too.
u) developers would like to publish apps with fixed foreign currency cost than converted numbers. For instance conversion of $1.50 might look like £1.10 based on conversion on that day. But selling it as £0.99 (exactly) does seem to boost sales.

--------

Yes, I do love the Android platform and have high regards for the entire team, great job guys; but these issues with market seem to be basic yet ignored/forgotten/unresolved as though tough, impossible or useless. Please!

At least initially, I shall refrain from posting 'when a feature/country will be added' sort of questions/issues here. There are many more issues important to many. Sorry for not posting those here.
Others who think there are other fundamental issues affecting many people, please feel free to reply to this post.
I'll update the post or at least keep those new ones for the next month's summary.
And do forgive my grammar/spellings/language/formatting/...
11/1/10
Posted by at No comments:

Wednesday, March 3, 2010

Welcome To The Google Experience!

This is a comical view of Google's Views, you can find this information right here on their site.


1. Focus on people – their lives, their work, their dreams.

The Google User Experience team works to discover people's actual needs, including needs they can't always articulate. Armed with that information, Google can create products that solve real-world problems and spark the creativity of all kinds of people. Improving people's lives, not just easing step-by-step tasks, is our goal.

Above all, a well-designed Google product is useful in daily life. It doesn't try to impress users with its whizbang technology or visual style – though it might have both. It doesn't strong-arm people to use features they don't want – but it does provide a natural growth path for those who are interested. It doesn't intrude on people's lives – but it does open doors for users who want to explore the world's information, work more quickly and creatively, and share ideas with their friends or the world.
So far google has been focusing on their own phone and providing this item for that phone only. Yes they made the Android Platform but they have not been very helpful since then...

2. Every millisecond counts.

Nothing is more valuable than people's time. Google pages load quickly, thanks to slim code and carefully selected image files. The most essential features and text are placed in the easiest-to-find locations. Unnecessary clicks, typing, steps, and other actions are eliminated. Google products ask for information only once and include smart defaults. Tasks are streamlined.

Speed is a boon to users. It is also a competitive advantage that Google doesn't sacrifice without good reason.
Wow Big Shocker Here! They have been wasting everyone's time, with this whole Market crap and not getting the Footprint uploaded... they could save everyone some time and fix the market to do copy protection based on IMEA numbers instead of blanketing phones based on a footprint just so they can prevent developer phones from accessing paid apps?

3. Simplicity is powerful.

Simplicity fuels many elements of good design, including ease of use, speed, visual appeal, and accessibility. But simplicity starts with the design of a product's fundamental functions. Google doesn't set out to create feature-rich products; our best designs include only the features that people need to accomplish their goals. Ideally, even products that require large feature sets and complex visual designs appear to be simple as well as powerful.

Google teams think twice before sacrificing simplicity in pursuit of a less important feature. Our hope is to evolve products in new directions instead of just adding more features.
Ok I'll give them this, They have made it simple.

4. Engage beginners and attract experts.

Designing for many people doesn't mean designing for the lowest common denominator. The best Google designs appear quite simple on the surface but include powerful features that are easily accessible to those users who want them. Our intent is to invite beginners with a great initial experience while also attracting power users whose excitement and expertise will draw others to the product.

A well-designed Google product lets new users jump in, offers help when necessary, and ensures that users can make simple and intuitive use of the product's most valuable features. Progressive disclosure of advanced features encourages people to expand their usage of the product. Whenever appropriate, Google offers smart features that entice people with complex online lives – for instance, people who share data across several devices and computers, work online and off, and crave storage space.
Well with the number of bugs in the system its turning away a bunch of people, Beginners and Experts.

5. Dare to innovate.

Design consistency builds a trusted foundation for Google products, makes users comfortable, and speeds their work. But it is the element of imagination that transforms designs from ho-hum to delightful.

Google encourages innovative, risk-taking designs whenever they serve the needs of users. Our teams encourage new ideas to come out and play. Instead of just matching the features of existing products, Google wants to change the game.

Ok they have been inovative, yet they have not been consistent with the who android project.


6. Design for the world.

The World Wide Web has opened all the resources of the Internet to people everywhere. For example, many users are exploring Google products while strolling with a mobile device, not sitting at a desk with a personal computer. Our goal is to design products that are contextually relevant and available through the medium and methods that make sense to users. Google supports slower connections and older browsers when possible, and Google allows people to choose how they view information (screen size, font size) and how they enter information (smart query parsing). The User Experience team researches the fundamental differences in user experiences throughout the world and works to design the right products for each audience, device, and culture. Simple translation, or "graceful degradation" of a feature set, isn't sufficient to meet people's needs.

Google is also committed to improving the accessibility of its products. Our desire for simple and inclusive products, and Google's mission to make the world's information universally accessible, demand products that support assistive technologies and provide a useful and enjoyable experience for everyone, including those with physical and cognitive limitations.
Well it seems they have only designed for certain countries, and will not even give a time frame for when others will be made available?

7. Plan for today's and tomorrow's business.

Those Google products that make money strive to do so in a way that is helpful to users. To reach that lofty goal, designers work with product teams to ensure that business considerations integrate seamlessly with the goals of users. Teams work to make sure ads are relevant, useful, and clearly identifiable as ads. Google also takes care to protect the interests of advertisers and others who depend on Google for their livelihood.

Google never tries to increase revenue from a product if it would mean reducing the number of Google users in the future. If a profitable design doesn't please users, it's time to go back to the drawing board. Not every product has to make money, and none should be bad for business.
Yeah Right!

8. Delight the eye without distracting the mind.

If people looked at a Google product and said "Wow, that's beautiful!" the User Experience team would cheer. A positive first impression makes users comfortable, assures them that the product is reliable and professional, and encourages people to make the product their own.

A minimalist aesthetic makes sense for most Google products because a clean, clutter-free design loads quickly and doesn't distract users from their goals. Visually appealing images, color, and fonts are balanced against the needs for speed, scannable text, and easy navigation. Still, "simple elegance" is not the best fit for every product. Audience and cultural context matter. A Google product's visual design should please its users and improve usability for them.
No problems here...

9. Be worthy of people's trust.

Good design can go a long way to earn the trust of the people who use Google products. Establishing Google's reliability starts with the basics – for example, making sure the interface is efficient and professional, actions are easily reversed, ads are clearly identified, terminology is consistent, and users are never unhappily surprised. In addition, Google products open themselves to the world by including links to competitors and encouraging user contributions such as community maps or iGoogle gadgets.

A greater challenge is to make sure that Google demonstrates respect for users' right to control their own data. Google is transparent about how it uses information and how that information is shared with others (if at all), so that users can make informed choices. Our products warn users about such dangers as insecure connections, actions that may make users vulnerable to spam, or the possibility that data shared outside Google may be stored elsewhere. The larger Google becomes, the more essential it is to live up to our "Don't be evil" motto.
So far the trust with google has gone out the door...

10. Add a human touch.

Google includes a wide range of personalities, and our designs have personality, too. Text and design elements are friendly, quirky, and smart – and not boring, close-minded, or arrogant. Google text talks directly to people and offers the same practical, informal assistance that anyone would offer to a neighbor who asked a question. And Google doesn't let fun or personality interfere with other elements of a design, especially when people's livelihood, or their ability to find vital information, is at stake.

Google doesn't know everything, and no design is perfect. Our products ask for feedback, and Google acts on that feedback. When practicing these design principles, the Google User Experience team seeks the best possible balance in the time available for each product. Then the cycle of iteration, innovation, and improvement continues.
And when we provide feed back Google has been either slow to respond or ignored the requests of developers and users a like...
Posted by at No comments:

Android Developers Actively Helping

Posted by at No comments:

Letter to Mobile Carrier's

Feel Free to copy and use this eMail to send to your Mobile Carrier.

You will NEED to enter your device info before mailing this

----

(Insert Your Devices Info Here - Found in "Settings/About Device(or Phone)")

Device Model:
Firmware version:
Baseband version:
Kernel version:
Build number:

(End Insert)

I'm sending you this in case you have made any changes to the Firmware/OS of my device after your received it from the manufacturer, in which case the modified Device Footprint that resulted needs to be submitted to Google's Android Market to allow "Copy Protected" apps to be viewed and downloaded from the Android Market.

This oversight is caused by one or more of you ,Google, or my device's manufacturer. So I am reporting it to YOU, Google, and my device's manufacturer.

For you to point the finger at Google, the device manufacturer, or the app's developer and tell me to contact them is irresponsible on your part as this issue is not a consumer issue, it is the responsibility of the you, Google, and the device manufacturer to ensure the device is listed properly with the android market. It is not the responsibility of the app's developer to ensure this device is listed properly so they can distribute their wares to this device.

If you choose to respond with finger pointing, although it is not my responsibility to facilitate the communication you should be having with that party yourself. Please be advised that all communication will be forwarded to the party with which you place the blame of the oversight. And may be made public on one or more websites.

Posted by at No comments:

Letter to Device Manufacturer's

Feel Free to copy and use this eMail to send to your device manufacturer.

You will NEED to enter your device info before mailing this

----

(Insert Your Devices Info Here - Found in "Settings/About Device(or Phone)")

Device Model:
Firmware version:
Baseband version:
Kernel version:
Build number:

(End Insert)


This Device Footprint needs to be submitted to Google's Android Market to allow "Copy Protected" apps to be viewed and downloaded from the Android Market.

This oversight can only be caused by one or both of you and, or Google. So I am reporting it to YOU and Google.

For you to point the finger at Google, my mobile carrier, or the app's developer and tell me to contact them is irresponsible on your part as this issue is not a consumer issue, it is the responsibility of the Device Manufacturer to ensure their device is listed properly with the android market. It is not the responsibility of the app's developer to ensure your device is listed properly so they can distribute their wares to this device.

If you choose to respond with finger pointing, although it is not my responsibility to facilitate the communication you should be having with that party yourself. Please be advised that all communication will be forwarded to the party with which you place the blame of the oversight.

Posted by at No comments:

Letter to Google

Feel Free To Copy and use this for your own email

You NEED to change *MANUFACTURER* to your Devices Manufacturer, and input your device details

---

(Insert Your Devices Info Here - Found in "Settings/About Device(or Phone)")

Device Model:
Firmware version:
Baseband version:
Kernel version:
Build number:

(End Insert)

This Device Footprint needs to be processed in to Android Market to allow "Copy Protected" apps to be viewed and downloaded from the Android Market.

This oversight can only be caused by one or both of you and, or *MANUFACTURER*. So I am reporting it to YOU and *MANUFACTURER*.

For you to point the finger at *MANUFACTURER*, my mobile carrier, or the app's developer and tell me to contact them is irresponsible on your part as this issue is not a consumer issue, it is the responsibility of YOU and the Device Manufacturer to ensure the device is listed properly with the android market. It is not the responsibility of the app's developer to ensure the device is listed properly so they can distribute their wares to this device.

If you choose to respond with finger pointing, although it is not my responsibility to facilitate the communication you should be having with that party yourself. Please be advised that all communication will be forwarded to the party with which you place the blame of the oversight.

Posted by at No comments:

Letter to App Developer's

Feel free to copy this letter to send to app developers when you can not find an app of theirs

-----

Unfortunately I seem to be having some issues with getting some apps from the market...
This problem only happens if your app is "Google copy protected" and is happening to a lot of devices not just mine

And your app is one of those.

So here is the skinny on my device

(insert your information here)

Carrier:
Voice Plan:
Data Plan:

(Insert your phone Information here - You can find your info in "Settings/About Device(or Phone)")

Device Model:
Firmware version:
Baseband version:
Kernel version:
Build number:

SD Card:

Firmware version = android OS version

(Be truthful here)

The phone is not rooted - has never been rooted
The phone has no mods done to it

Location: Your City - Your State - Your Country

After through searching, I found that this website http://androidissues.blogspot.com/ and it seems to be a problem with "new devices." The device manufacture is supposed to send the device's footprint signature to Google for the "Google copy protection" to work, and until this has been resolved any app in the market that has "Google copy protection" will not show up in searches for a new device. By new device, I mean either a device that has just come out, or an old device that has had the OS updated.

On that site they have an image of what error I get when I try searching for your app.

Why am I telling you this, because it’s hurting your sales, and even your ratings?

What you can do about this?

Please Visit This Site http://androidissues.blogspot.com/ to learn more about this error/issue, Once you have read the webpage above, you could help get this issue resolved, by contacting Google and my device's manufacturer. I have included links to their contact pages for you. Please use the device info above when contacting them.

Email Google:
Http://www.google.com/support/androidmarket/bin/request.py?contact_type=publisher
Inform them that the footprint for the device needs to be processed by the market, and you are losing business because it is not processed.

(Insert Manufacturer's email Support Link here)

And tell them the same thing; you need the devices footprint submitted to Google android market as you are losing business.

No matter how much you complain these guys will continue to point the finger at each other, just keep replying to their emails and copy Google’s response to the manufacturer and the manufacturer's to Google, thereby getting them to communicate to each other

Why do you need to do this instead of me? Well I have already done this, and you should ask your clients to also contact these guys, but you also need to contact them as you are the one who is really missing out, for those apps that are paid you lose money, for those that are free you get a bad rep as a developer.

So in conclusion thank you for your time and understanding in this issue.
And if you are developing free apps in the future please do not mark these free apps as copy protected. For the paid apps I don't really know what else to say.

After all of this, can you please provide a way for me to get your app other than the android market?

Thank you
(Your Name Here)

Posted by at No comments:
Subscribe to: Posts (Atom)