All About Android 180
Topic: Developers required to list their address to the public, encryption on by default, Amazon's new Kindle lineup, running any Android app in the Chrome browser, and more!
Recorded: September 23 2014
All About Android 180: Trolled By a Listicle
- Google Will Now Require All App Publishers With Paid Apps Or In-App Purchases To Have An Address On File And Displayed Publicly In Google Play
- A new policy for developers is about to roll out by Google requiring devs to add a physical address to their public profile, mandatory for those who feature any paid apps of any sort. PO boxes are also not allowed. This address will be visible to all Play Store users. If developers don't do this, their app can be pulled from the store.
- Google says the change is the result of "consumer protection laws and current best-practices" and will take effect September 30.
- Should be noted that the consumer protection laws in question here are likely referring to an EU consumer right directive.
- Some folks in a subreddit post on the issue claim that going to a UPS store and getting a mailbox results in a physical address and not a PO box so that might work.
- "Google will require public display of *home* addresses by indie devs on 30 September - no PO boxes allowed "
- Koush's story on this subject
- Google Play soon will list in-app purchase price ranges
- Another part of Google's answer to this has been the fact that, also starting Sept 30, Google will begin to display the range of prices an app can charge with in-app purchases on the Play Store. This is an answer to the recent dustup over children racking up in-app purchases and their unknowing parents footing the bill.
- Google revealed some new security insight into Version L: Full disk encryption, on by default. This, of course, addresses a hot button issue at the moment by making it more difficult for law enforcement to gain access to a user's smartphone data. Apple made the same announcement last week for it's iPhone. Encryption on Android isn't new, but it was off by default.
Hi AAA Team - I was listening to the most recent show and I would like to clear some things up about Apple Pay. I used to work doing development of contactless payment terminals for one of the largest manufacturers of credit card processing terminals so I know what I'm talking about.
With that as a preface the first thing that I'd like to point out is that Apple Pay is just a standard contactless credit card transaction. While it is possible to configure a terminal to only accept cards from certain issuers most large merchants - who purchase and program their own terminals (as opposed to those received from abank or processor which many of the smaller merchants use) - will not want to limit acceptance of credit cards only to specific issuers because it's not in their interest. In addition, you can't configure the terminal such that it will accept everything EXCEPT Google Wallet or Softbank.
I would imagine that the vending machines that you guys talked about during the show were doing one of the following: - Running specific, custom software that checked for Softbank authentication before allowing a credit card transaction to go through. - Limiting acceptance to just cards issued by Softbank (much easier and cheaper). I can't see any of the retailers noted as supporting Apple Pay - many of whom already accept contactless payment - making major changes to their POS software to limit the acceptance to just people paying with an iPhone nor can I see them risking disenfranchising already existing customers who are used to paying with contactless be it Google Wallet or a plastic card.
- New Kindle hardware!
- Updated Kindle Fire HDX
- 8.9" 2560x1600 339ppi display, 2.5GHz Snapdragon 805 quad-core processor -$379
- Kindle Fire HD 6 - $99
- Kindle Fire HD 7 - $139
- Both with MediaTek 1.5GHz quad core processor, bold color options, front and rear facing cameras, Shipping next month
- Fire HD Kids Edition - 6" $149, 7" $189
- No questions asked 2 year guarantee with replacement at no charge, one year of Amazon FreeTime Unlimited (books, movies, tv shows, games, all you can eat), rubber bumper and spill resistant, can set screen time limits on app usage and times within which the tablet can even be used. Pre-order now, ships October 21.
- Fire OS 4 (aka Sangria)
- Family profiles, content sharing between family members, pre-caching of video it thinks you want to watch (aka ASAP: Advanced Streaming and Protection), Smart Suspend for learning your usage patterns and doing things like deactivating WiFi when not at home, Firefly, KitKat.
- Amazon Announces The Fire HD Kids Edition With A No Questions Asked Two-Year Guarantee
- Amazon's Fire OS 4 Brings New Coat Of Paint, 'Hundreds Of New Features' Including Firefly, Profiles
- HTC Returns to Tablets with Google Nexus Partnership
- Rumor time: Take this block with a grain of salt, though the Wall Street Journal is reporting part of it so...:
- First, the Nexus 9, expected to be an HTC tablet accord to WSJ, is looking like it might get an unveiling October 15th or 16th, along with more new hardware (a Nexus phone of some sort? Moto Nexus perhaps?) and "new software", likely Version L. Release date for Version L is said to happen November 1st (though come on, I'm guessing Halloween like it did with KK), and no word on if the new devices will release at that time or not.
- Exclusive: Next-gen Nexus hardware to be unveiled in mid-October, Android L hits November 1st
- Oculus CTO John Carmack: Samsung Let Us Bypass Android “Development Hell”
- John Carmack, CTO of Oculus since last year, said that developing for Android was more or less a nightmare. "I’ve got a lot of negative things to say about the Android development experience… Some of them are fundamental." Which is why the Samsung deal happened. He said that by targeting one device (the Note 4), Oculus could "bypass the development hell of Android" bringing the process closer to that of developing for a console. "This project was nice [because of] the tight partnership with Samsung."
Hello Jason, Gina, Ron, Brian, and esteemed guest,
I recently got the Moto 360 after months of hype and wanting it. Though it wasn't as great as I hoped, I was still very happy with it, particularly with voice texting and not having to check my phone every time I get a notification. Buuuuuut... Tonight I charged it to full and noticed a red halo around the edge that looked suspiciously like a screen burn effect. The watch was also really hot.
When I noticed this supposed screen burn on a device that cannot experience screen burn (LCDs to my knowledge don't have this issue) I was naturally upset. Calmly (versus angrily) I restarted my Moto 360 and, to my chagrin, the ""burn"" effect was still there.
I only had the watch for a week and a half and did put it through its paces (walking in the rain, exercising with it, constant use of voice commands for texting and other apps, etc.). I reached out to Motorola support and am considering returning it to Best Buy for a full refund, with no exchange possible due to no stock available. This is my first Android wear experience and I have a thick enough skin to not get too disappointed in the Moto 360 on this issue.
Thanks guys, big fan of the show here! Keep on trekking!
...45 minutes LATER: ... The red halo all but vanished completely. Hoping by morning it'll be completely gone. Then, I will not be returning it."
- Remember how Chrome OS is beginning to run certain Android apps natively? Well, no anyone with a Chrome browser can run practically any Android app, thanks to some clever engineering by folks who know what their doing. Chrome 37+ is required to do this, and the process involves installing a new runtime (ARChon runtime) that enables android apps in Chrome. Then the user, armed with an APK, can actually spoof the signed keys of those four apps we discussed last week that Google officially allows. The process is detailed, and Eric Ravenscraft of Lifehacker lists them all out for you.
- We've heard all about Material Design and how Google promises to unify its offerings look-and-feel across all platforms. A piece of that puzzle is the Polymer framework, first shown at last year's IO and then revealed in more detail at this year's IO. Polymer is a development kit that gives developers Material Design for the web. Its a library that enables a quick and easy way to build web applications that are capable of running like native apps.
- To show off what Polymer can do, Google launched Topeka, a quiz app, to the Play Store. It shows off the result of Polymer in action, and by extension, web apps running natively on Android. Inside Topeka you'll see all the keystones of material design.
I released an app!
I've always had a soft spot for Grooveshark. One of my favorite parts of Grooveshark was being able to send anyone a link and know that it would play in their browser.
Eventually I got a little sick of the mess that Grooveshark's library was in (and too much time around Google rubbed off on me) and I switched to Google Music All Access. It's lovely but now when I send my friends a link they hit a pay wall!
So that's where Shark Share comes in, it pulls the song and artist name from the Subject Line of shared songs and searches Grooveshark for them. I've tested it with Google Music and Spotify.
- Last Week's Poll
- Ron - Wear Tip Calculator (FREE/IAP)
- Jason - Delayed Lock (TRIAL/$2.99)
- Gina - HeadsUp (FREE/IAP)
- This Week's Poll
- Ad Time: 24:40
- Ad Time: 53:16
- Ad Time: 1:05:21
- Edited by:
|This area is for use by TWiT staff only. Please do not add or edit any content within this section.|