Articles by "tablet"
Showing posts with label tablet. Show all posts
Tech Touchz is a Network about Hacker News, Tech News &Tech Hacks - Latest &Tech News, Hacker News and Hacking Tricks About Technology

Apple’s iTunes Allowances will be shut down next month

Apple is discontinuing support for iTunes Allowances, the feature that allowed parents to send monthly credits to a recipient’s – meaning, their child’s – Apple ID for use in the iTunes Store.


 That allowance could then be spent on music, videos, apps or books, as the child desired. Now, according to an update to the iTunes Allowances support page on Apple’s website, the feature is being shut down, and existing allowances will cancel on May 25, 2016.

That means the installment payments will no longer be delivered after that date, but the unused credit will not actually disappear. Apple says that credit will remain in the recipient’s account until it’s used.

Allowances were useful for parents who wanted a way to control spending and set limits on what their kids could buy from the iTunes Store every month. And they offered a nice alternative to having to constantly deal with nagging kids, begging for new apps and games.

With the feature’s shutdown, Apple is directing customers to use “Family Sharing” instead. Introduced in 2014, Family Sharing lets up to six people share media purchases, including iTunes music, movies, TV shows, books and apps, without having to share accounts. The idea is that purchases could be paid for using one credit card, while parents could also approve kids’ spending requests from their own devices.

In addition to sharing media, the feature can also be used to share photos, a family calendar and more between devices, including iPhone, iPad, iPod touch, and Mac. It requires iOS 8 or later; OS X Yosemite or later; and iTunes 12. PC users can also take advantage of the feature via iCloud for Windows.

One of the more useful aspects to Family Sharing versus iTunes Allowances is that it permits kids under 13 to have their own Apple IDs, as they’re managed as part of the family group. Organizers can also limit access to content on their kids’ devices using iOS’s “Restrictions” or OS X and iTunes’ parental controls.

However, the feature still needs improvement in other areas. Namely, it doesn’t support in-app purchases, which is a common request from kids. (iTunes Allowances did.). Some parents also find it frustrating to have to manually approve every iTunes purchase request, too. But that’s because they may not realize the “Ask to Buy” option can be disabled for kids and other members.

MacRumors first spotted the feature’s shut down, noting that Apple customers were being informed of the closure via email. While Apple didn’t give an official reason for ending iTunes Allowances, it makes sense. There’s no need for both options, given how much overlap there is between the two services.
Tech Touchz is a Network about Hacker News, Tech News &Tech Hacks - Latest &Tech News, Hacker News and Hacking Tricks About Technology

Meet Oasis, Amazon’s smaller, lighter, grippier Kindle

True to earlier reports, Amazon’s Kindle Oasis is the smallest and lightest Kindle yet and comes with a handle for gripping.

Amazon’s Jeff Bezos teased an “all-new, top of the line” Kindle last week and Chinese site Tmall.com sent the e-reader world in a tizzy when it accidentally unveiled details of Kindle’s newest addition to the family on Monday.

The site quickly took the page down, but not before the tech press caught wind of it.
The latest Kindle steps ever closer to that real book feel with just 3.4 mm at its thinnest point and the new one-sided handle grip is designed to make you feel like you’re holding the spine of a book while reading.
Meet Oasis, Amazon’s smaller, lighter, grippier Kindle

Left-handed bibliophiles might be concerned about a new back bump that seems designed for all the righties like in the picture above, but you can actually flip the Oasis and grip from either hand.


You can still flip pages using the touch display if you prefer. Amazon says it’s “all about choice.”

The Oasis is noticeably smaller than Voyager, weighing a total of 4.6 ounces, or roughly the same as a deck of cards – a manageable weight for taking along without adding too much to your load – and 20 percent lighter than any other Kindle.

The thinner and lighter design still maintains a high-resolution 300 ppi Paperwhite display and comes with an even crisper and brighter front light for improved night reading. The lighting is also on the side instead of the bottom like with Voyager for a brighter and more evenly lit screen.

Earlier rumors also mentioned a solar powered case for the new Oasis. While that turned out to be a red herring, it does have a longer-lasting dual battery system. The smaller, built-in battery cell will last up to two weeks and the included charging cover adds a continuous charge of up to two months of life to the newest Kindle.

Covers will come in walnut, merlot or black and can charge at the same time as you are charging your Kindle.Oasis will still display Amazon’s signature Bookerly (seraph font) or Amazon Ember (sans seraph) and will pull up your GoodReads list.

The redesigned Kindle Store will also help newer Kindle readers find and define the types books they’d like to read in the future.
Tech Touchz is a Network about Hacker News, Tech News &Tech Hacks - Latest &Tech News, Hacker News and Hacking Tricks About Technology

MediaPad

Back in February right before Huawei's MWC event an upcoming tablet by the Chinese manufacturer got leaked. However, the MediaPad T2 10.0 Pro, for that's its name, wasn't actually made official that time around. Huawei has yet to acknowledge it, but the slate has been leaked again today - so maybe its announcement is close by.

The new MediaPad has received the leaked press render treatment, with official-looking shots depicting it from a few angles.Alongside the new images we also get a confirmation of its specs, which were first outed in February. The MediaPad T2 10.0 Pro will basically be a slightly watered down version of the MediaPad M2. 

It will come with a 10.1-inch 1,920x1,200 IPS touchscreen, Qualcomm's Snapdragon 615 SoC at the helm (with a 1.5 GHz octa-core Cortex-A53 CPU), 2 or 3GB of RAM, 16 or 32GB of expandable storage, an 8 MP rear camera with LED flash, a 2 MP selfie shooter, and a 6,660 mAh battery. Disappointingly it runs Android 5.1.1 Lollipop.

LTE connectivity will be available on some models, which will obviously be more expensive than the Wi-Fi-only iterations. Speaking of which, the starting price in Europe is apparently going to be around €280, while for an LTE-capable tablet you'll need to pay €350. The MediaPad T2 10.0 Pro is 8.5mm thin and it weighs 495g. It will be offered in two color versions - white and black. The slate will be the successor to the T1 from last year.
Tech Touchz is a Network about Hacker News, Tech News &Tech Hacks - Latest &Tech News, Hacker News and Hacking Tricks About Technology
The open source VoIP engine and standards initiative, known as WebRTC, is finally starting to get some traction. Earlier this month, Slack followed Facebook Messenger’s lead and launched its voice calling feature based on WebRTC. Though exciting, this launch is limited — it only works within Slack’s desktop apps and Chrome.

We can presume it’s just in MVP mode and that Firefox support will come soon, given the minimal incremental effort to support that platform. Internet Explorer and Edge, its WebRTC-supporting upgrade, are likely a non-factor for Slack users. That leaves support for Apple’s Safari browser next on the list.

Does it matter that Safari does not support WebRTC? Safari has been lagging on the web for a while — does Apple even care?

 Apple?

Does WebRTC need Apple?


Safari has been a perennial thorn in WebRTC’s side. Depending on who is counting, Safari has roughly a 10-15 percent share of the total browser market across desktop and mobile. The stats don’t indicate that changing much over time. A flat 10-15 percent is not insignificant, but it’s not really big enough to get initial priority when developing a new web app. Does that change when your user base grows and you can afford to provide broader support?

Facebook certainly doesn’t seem to care. Try to make a call through the Messenger interface on the web with Safari and you’ll get this:



They don’t even attempt to hide the call buttons to prevent users from trying to make calls on Safari. They keep the phone and video call buttons there, enticing you to click so they can try to convince you to use another browser. If Facebook doesn’t care about supporting Safari for its 800-plus million Messenger users, it’s hard to make a case that anyone else should, too.

However, Safari is not a WebRTC developer’s biggest problem: Apple’s iOS policy is. Apple requires that you use its web-rendering engine. It doesn’t matter if you’re a small startup or Google with its Chrome browser: If you want to build an app that renders a web page, you need to use Apple’s WebView API.

Apple can monetize apps via the app store; it can’t monetize web visits through a browser.
There is no such thing as WebRTC on the mobile web for iOS. This means that Google and other developers can’t support WebRTC on iOS devices unless it’s built into a native iOS app. That is a serious blow to web advocates’ vision of a ubiquitous world wide web for all devices. From the App Store review guidelines: “Apps that browse the web must use the iOS WebKit framework and WebKit Javascript.”

Does Apple need WebRTC?

WEbtc techtouchz

Apple has its own VoIP app that it puts on all its devices — FaceTime. The FaceTime app works just fine on Apple devices without WebRTC. Steve Jobs mentioned in 2010 that Apple would move to make FaceTime an open standard. This could have mitigated the need for the WebRTC standard in the first place. Then, in 2012, Apple was sued by a patent troll around this tech and lost. Since then, Apple has kept quiet about opening FaceTime, and there is no reason to think that will change.

Apple’s web renderer policy on iOS has the effect of forcing WebRTC developers to create iOS apps for their devices. Apple can monetize apps via the app store; it can’t monetize web visits through a browser.

WebRTC is not the only casualty of Apple’s policy (see the full list versus Firefox here). Despite the low market risk in supporting many modern web features, Safari is way behind. Apple certainly has the resources to do whatever it wants. Its huge and growing backlog is certainly an indicator that the web hasn’t been a big priority. Even if this suddenly changed, WebRTC would be just one of many features competing for internal attention.

Apple being Apple, we will never really know what is going on until they are ready to announce something.
Historically, the world’s most valuable company has not had much incentive to do anything different. If Apple can survive by ignoring web, why would it care about a single web standard like WebRTC?

Can Apple buck the status quo forever?


The short answer is “no.” Apple’s strategy of dragging down the web, and making developers’ lives more difficult, cannot be sustained indefinitely. If it pushes too much against the status quo of the rest of the market, it risks alienating its constituents rather than endearing them.

Thanks to WebRTC, VoIP calling has moved from being a magical, technical feat that few could master, to an easy-to-add feature to any app. If Safari won’t support WebRTC, developers will likely direct those customers to something other than Safari, just as Facebook has done. Apple may not have ambitions of creating the No. 1 browser, but I’m sure they would still like Safari to be competitive. With Google, Amazon, Snapchat and now Slack providing WebRTC as a feature, we’re at the point where many developers want to do the same.

Apple also has pressure on the iOS app-development front. Building WebRTC for iOS from the source repositories is a lot easier than it used to be, but it’s still not as simple as using the web APIs. To get there, WebRTC really needs to be added to iOS’s native web view, just like it is in Android with Google.

Of course, there are always third-party libraries to help in the interim, but third party and commercial is never as attractive as free and native to developers.

Does Apple want to change?


Guess what? Apple has been spotted advertising WebRTC developer roles for WebKit (its web rendering engine).



It seems Apple really is feeling the pressure. This is certainly good news for web and WebRTC advocates. Community efforts like webrtcinwebkit.org should make it much easier for Apple’s new WebRTC engineers when they are hired.

Apple being Apple, we will never really know what is going on until they are ready to announce something. Still, it seems WebRTC’s initial vision of universal browser support will be a reality at some point in the near future. It just goes to show, you can’t ignore your customers’ demands forever.