Welcome. Here you find latest freeware and legal software as well as latest info about IT Technology.
Showing posts sorted by relevance for query apple. Sort by date Show all posts
Showing posts sorted by relevance for query apple. Sort by date Show all posts
Samsung Group scored a victory over rival Apple Inc in their long-running dispute over mobile device patents after a US trade agency issued an order banning older but still-popular Apple products like iPhones and iPads from the US market.

The US International Trade Commission (ITC) ruled on Tuesday that the Silicon Valley giant had infringed on a patent owned by Samsung Electronics that involves the ability of devices to transmit multiple services simultaneously and correctly through 3G wireless technology.

The independent federal agency slapped a ban on the import

Apple's smartwatch leapt to the lead in wearable computing on strong sales of it. (A market survey shows)

Apple smartwatch silver and golden
The survey released Thursday by Strategy Analytics showed Apple grabbed a 15.9% share of the wearables market in the first quarter.
While Apple does not release sales figures for its Apple Watch, the estimate by Strategy Analytics showed a 59% jump in sales from a year earlier, with 3.5 million units sold in the first three months of the year."The new Apple Watch Series 2 is selling relatively well in the US, UK and elsewhere, due to enhanced styling, intensive marketing and a good retail presence," said Strategy Analytics executive director Neil Mawston.
iPad with iOS 11

Apple's iOS 11 brings lot of new features to iPad users such as handy apps dock for quick navigation between apps and implement extra features for the use of Apple's Pencil with iPad iOS11. Now I am revealing some great and hidden features of iOS 11 for Apple's iPad.

Apple's iPad getting advance day by day, its upgraded hardware meeting with latest technology make iPad better and more better with every passing year.

In 2017, Apple pushed out iOS 11, its best software to date. This latest release is especially lovely news for iPad owners as the tablet has received a lot of attention, with a revamped interface to help speed up everyday operation.

Apple iOS 11.1 New Emoji
Apple on Friday revealed the new emoji that will be making their way to iOS 11.1 coming later this year. With thousands of emoji available on iPhone, iPad, Apple Watch and Mac.

New emoji include Woman with Headscarf, Bearded Person and Breastfeeding, and food items such as Sandwich and Coconut. More animals and mythical creatures like T-Rex, Zebra, Zombie and Elf are a fun way to describe situations and new Star-Struck and Exploding Head smiley faces make any message more fun.

Why former Apple CEO Steve Jobs cried in front of his co-workers?

A formal CEO Steve Jobs

Steve Jobs - as brilliant as he was - is sometimes remembered for his not-so-nice side. For example, he often told his engineers, "This is s---" when reviewing their work, according to Walter Isaacson's biography of Steve.

But former Apple chief executive John Sculley, 76, says that was just one side of Steve. "So many of the movies and portrayals of Steve Jobs just focus on the 'bad boy' Steve, or the idea that he wasn't perfect," Sculley said. "But they don't explain why so many people loved working for him as difficult as he was, and the reason is because he was an incredibly emotional person."

The biggest difference between iOS and Android has always been simple: Apple makes its own phones, operating system and cloud back-end, and sells essentially a single model of phone and a single model of tablet. By contrast, Google drives an open-source mobile platform, which is supported by a rich network of competing hardware makers who innovate on
Its time for Augmented Reality(AR) to shine.

When Google announced its Daydream View headset last year, it was a sign that the search giant was ready to take VR to the masses. It's dabbled in VR before with Cardboard, but the View was a much more serious effort, with its fabric-clad design and user-friendly remote. Which is why it's such a surprise that Google didn't really spend a lot of time on VR at its Pixel 2 event. The company mentioned the new Daydream View -- now in colors! -- but didn't really say much more beyond that. Instead, Google was much more excited to talk about something else: AR.

Some tough questions that was asked in interview at  top most  companies like Google, Apple, Microsoft Twitter, and others.

google interview
image credit: alltechbuzz.net
  • Google - Administrative Assistant.Question: If you were given a box of pencils, list 10 things you could do with them that are not their traditional use.
  • Google - Project Manager.Question: You want to design a phone for deaf people — how do you do it?
  • Apple - Intern
    Question: What's the most creative way you can break a clock?


What do chip makers like AMD, ARM, Samsung, MediaTek, Qualcomm, and Texas Instruments have in common? Well, apart from the obvious similarities between these chip-making behemoths, they also happen to be founders of the HSA Foundation. What’s HSA, and why does it need a foundation backed by industry heavyweights?
In this post I will try to explain why HSA could be a big deal in the near future, so I’ll start with the basics: What is HSA and why should you care?
HSA stands for Heterogeneous System Architecture, which sounds kind of boring, but trust me, it could become very exciting, indeed. HSA is essentially a set of standards and specifications designed to allow further integration of CPUs and GPUs on the same bus. This is not an entirely new concept; desktop CPUs and mobile SoCs have been employing integrated graphics and using a single bus for years, but HSA takes it to the next level.
Same load, different architectures: CPUs and GPUs excel at different tasks. What happens when they start sharing the load, with no developer input?
Same load, different architectures: CPUs and GPUs excel at different tasks. 
What happens when they start sharing the load, with no developer input?

Google on Monday reported that its Chrome program for Windows was being updated, coordinating its Chrome Cleanup device to expel destructive programming. The new device does not supplant any broadly useful antivirus, and rather, utilizes a discovery motor created by IT security organization ESET for Chrome's sandbox, with the point of conveying a more secure perusing knowledge. The inherent device, which is currently taking off to Chrome for Windows, won't be accessible on Chrome for macOS or Linux.


  • Chrome Cleanup tool was previously standalone for Windows
  • It is now integrated into the Chrome browser
  • The update is now rolling out to Windows users
HACKERS can target almost ANY smart device around the world thanks to a vulnerability in WPA2 Wi-Fi security. Here's everything you should know about this threat.

PUBLISHED: 09:20, Tue, Oct 17, 2017 | UPDATED: 09:20, Tue, Oct 17, 2017

Apple iOS, Windows, Android and any smart device that uses Wi-Fi are all at risk of an attack, cybersecurity experts have warned today.

The newly discovered KRACK exploit affects the WPA2 security protocol, a standard for Wi-Fi security used on almost every Wi-Fi router.

In theory it allows a hacker within range of a Wi-Fi network to read passwords, credit card numbers and photos sent over the internet.  

Other sensitive information that can be obtained thanks to this exploit is chat app messages and e-mails.

Top 10 Most Common Mistakes That Android Developers Make: A Programming Tutorial


Android. What’s not to like about this platform? It’s free, it’s customizable, it’s rapidly growing and it’s available not just on your phone or tablet, but on your smartwatch, TV and car too.
With the latest Lollipop update, Android programming continues to improve. The platform has matured quite a bit since the initial AOSP release, and set the user expectations bar quite high. Look how good the new Material design pattern looks!
There are thousands of different devices, with different screen sizes, chip architectures, hardware configurations, and software versions. Unfortunately, segmentation is the price to pay for openness, and there are thousands of ways your app can fail on different devices, even as an advanced Android programmer.
Regardless of such huge segmentation, the majority of bugs are actually introduced because of logic errors. These bugs are easily prevented, as long as we get the basics right!
Here’s an Android programming tutorial to address the 10 most common mistakes Android developers make.
Learn Android programming at a more advanced level with this tutorial.

Common Mistake #1: Developing for iOS

To my great pleasure, this Android mistake is far less common nowadays (partially because clients are beginning to realize that the days when Apple was setting all the design standards are long gone). But still, every now and then, we see an app that is an iOS clone.
Don’t get me wrong, I’m not an Android programming evangelist! I respect every platform that moves the mobile world a step forward. But, it’s 2014 and users have been using Android for quite a while now, and they’ve grown accustomed to the platform. Pushing iOS design standards to them is a terrible strategy!
Unless there is a super good reason for breaking the guidelines, don’t do it. (Google does this all the time, but never by copy-pasting.)
Here are some of the most common examples of this Android mistake:
  1. You should not be making static tabs, and they don’t belong on the bottom (I’m pointing at you Instagram).
  2. System notification icons should not have color.
  3. App icons should not be placed inside a rounded rectangle (unless that’s your actual logo ex. facebook).
  4. Splash screens are redundant beyond the initial setup/introduction. Do not use them in other scenarios.
  5. Lists should not have carets.
These are just a few of the many other small things that can ruin the user experience.

Common Mistake #2: Developing for Your Android Device

Unless you are building a kiosk/promo app for a single tablet, chances are your Android app won’t look good on every device. Here are a few Android programming tips to remember:
There are literally thousands of possible scenarios, but after a while you develop a sense for covering them all with a handful of cases.
You don’t own thousands of devices? Not a problem. The Android Emulator is super good in replicating physical devices. Even better, try out Genymotion, it’s lightning fast and comes with a lot of different popular preset devices.
Also, have you tried rotating your device? All hell can break loose…

Common Mistake #3: Not Using Intents

Intents are one of Android’s key components. It’s a way of passing data between different parts of the app or, even better, different apps on the system.
Let’s say you have a gallery app that can share a download link to some images via SMS. Which of the two options seems more logical?
Option 1:
  • Request the SEND_SMS permission.
  • Write your own code for sending SMS using the SmsManager.
  • Explain to your users why your gallery app needs access to services that can cost money, and why they have to grant this permission to use your app.
Option 2:
  • Start an SMS Intent and let an app designed for SMS do the work
      Intent sendIntent = new Intent(Intent.ACTION_VIEW);
      sendIntent.setData(Uri.parse("sms:" + telephoneNumber));
      sendIntent.putExtra("sms_body", x);
In case that you have any doubts, best solution is option 2!
This approach can be applied to almost anything. Sharing content, taking pictures, recording video, picking contacts, adding events, opening links with native apps, etc.
Unless there is a good reason to make a custom implementation (ex., a camera that applies filters), always use Intents for these scenarios. It will save you a lot of programming time, and strip the AndroidManifest.xml of unnecessary permissions.

Common Mistake #4: Not Using Fragments

A while ago in Honeycomb, Android introduced the concept of fragments. Think of them as separate building blocks with their own (rather complex) life cycles that exist inside an Activity. They help a lot with optimizing for various screens, they are easily managed by their parent activity, can be reused, combined and positioned at will.
Launching a separate activity for each app screen is terribly inefficient, since the system will try to keep them in memory as long as it can. Killing one won’t free the resources used by the others.
This Android programming tutorial recommends the proper use of fragments to make your app more efficient.
Unless you want to dig deep into the Android core and read this article, advocating against fragment usage, you should use fragments whenever possible. It basically says that fragments and cursor loaders have good intended purpose, but poor implementation.

Common Mistake #5: Blocking the Main Thread

The main thread has a single purpose: keeping the user interface responsive.
Although the science behind measuring the frame rate our eyes/brain can perceive is complex and influenced by a lot of factors, a general rule is that anything below 24 fps with delay greater than 100 ms won’t be perceived as smooth.
This means that the user’s actions will have a delayed feedback, and the Android app you have programmed will stop responding. Stripping the user of his control over the app leads to frustration, frustrated users tend to give very negative feedback.
Even worse, if the main thread is blocked for a while (5 seconds for Activities, 10 for Broadcast Receivers), ANR will happen.
As you learn Android programming, you will come to know and fear this message.  Follow these Android programming tips to minimize this occurrence.
This was so common in Android 2.x, that on newer versions the system won’t let you make network calls in the main thread.
To avoid blocking the main thread, always use worker/background threads for: 1. network calls 2. bitmap loading 3. image processing 4. database querying 5. SD reading / writing

Common Mistake #6: Reinventing the Wheel

“OK, I won’t use the main thread. I’ll write my own code that communicates with my server in a background thread.”
No! Please don’t do that! Network calls, image loading, database access, JSON parsing, and social login are the most common things you do in your app. Not just yours, every app out there. There is a better way. Remember how Android has matured and grown as a platform? Here’s a quick list of examples:
  1. Use gradle as a build system.
  2. Use Retrofit / Volley for network calls.
  3. Use Picasso for image loading.
  4. Use Gson / Jackson for JSON parsing.
  5. Use common implementations for social login.
If you need something implemented, chances are it’s already written, tested and used widely. Do some basic research and read some Android programming tutorials before writing your own code.

Common Mistake #7: Not Assuming Success

Great. We have learned that there is a better way for handling long running tasks, and we are using well documented libraries for that purpose. But the user will still have to wait. It’s inevitable. Packages are not sent, processed and received instantly. There is a round trip delay, there are network failures, packages get lost, and dreams get destroyed.
But all this is measurable. Successful network calls are far more likely than unsuccessful ones. So why wait for server response before handling the successful request? It’s infinitely better to assume success and handle failure. So, when a user likes a post the like count is immediately increased, and in unlikely event that the call failed, the user is notified.
In this modern world immediate feedback is expected. People don’t like to wait. Kids don’t want to sit in a classroom obtaining knowledge that has uncertain future payoff. Apps must accommodate to the user’s psychology.

Common Mistake #8: Not Understanding Bitmaps

Users love content! Especially when the content is well formatted and looks nice. Images, for instance, are extremely nice content, mainly due to their property of conveying a thousand words per image. They also consume a lot of memory. A lot of memory!
Before an image is displayed on the screen, it has to be loaded into the memory. Since bitmaps are the most common way to do this, we’re going to provide an Android programming guide for the whole process:
Let’s say you want to display an image on your screen that you just took with your camera. The total memory needed for this is calculated with the following formula: memory_needed_in_bytes = 4 * image_width * image_height;
Why 4? Well, the most common / recommended bitmap configuration is ARGB_8888. That means that for each pixel we draw, we need to keep 8 bits (1 byte) for the alpha, the red, the greed and the blue channel in memory, in order to properly display it. There are alternatives, like the RGB_565 configuration that requires half the memory than ARGB_8888, but loses the transparency and the color precision (while maybe adding a green tint).
Let’s assume you have a brand new device with full HD screen and 12 MP camera. The picture you just took is 4000x3000 pixels large and the total memory needed to display it is: 4 bytes * 4000 * 3000 = 48 MB
48 megabytes of your RAM just for a single image!? That’s a lot!
Now let’s take the screen resolution into consideration. You are trying to show a 4000x3000 image on a screen that has 1920x1080 pixels, in worst case scenario (displaying the image full screen) you shouldn’t allocate more than 4 * 1920 * 1080 = 8.3 MB of memory.
Always follow the Android programming tips for displaying bitmaps efficiently:
  1. Measure the view you’re showing your images in.
  2. Scale / crop the large image accordingly.
  3. Show only what can be displayed.

Common Mistake #9: Using Deep View Hierarchy

Layouts have an XML presentation in Android. In order to draw content, the XML needs to be parsed, the screen needs to be measured, and all the elements need to be placed accordingly. It’s a resource- and time-consuming process that needs to be optimized.
This is how the ListView (and more recently the RecyclerView) works.
If a layout has been inflated once, the system reuses it. But still, inflating the layout must happen at some point.
Let’s say you want to make a 3x3 grid with images. One way of doing this is a vertical LinearLayout containing 3 LinearLayouts with equal weight, each of them containing 3 ImageViews with equal weight.
Some Android programming beginners don’t always make the best use of LinearLayouts.
What do we get with this approach? A warning that “nested weights are bad for performance”.
There is a saying in the Android programming world, that I just made up: “With little effort all hierarchy can be flattened”.
In this case RelativeLayout or GridLayout will efficiently replace the nested LinearLayouts.

Common Mistake #10: Not Setting the minSdkVersion to 14

Well, this is not a mistake, but it is bad practice.
Android 2.x was a huge milestone in developing this platform, but some things should be left behind. Supporting older devices adds more complexity for code maintenance and limits the development process.
The numbers are clear, the users have moved on, the developers shouldn’t stay behind.
I’m aware that this doesn’t apply for some big markets with old devices (ex. India), and setting the minSdkVersion to 14, on the Facebook App, means leaving couple of million users without their favorite social network. But, if you are starting fresh and trying to create a beautiful experience for your users, do consider eliminating the past. Users that don’t have the resources, or feel the need to upgrade their device/OS, won’t have the incentive to try out a superior version of your Android app and ultimately spend money on it.

Wrap Up

Android is a powerful platform that evolves quickly. It may not be reasonable to expect users to keep up the pace, but it’s crucial for the Android developers to do so.
Knowing that Android is not just on our phones or tablets is even more important. It’s on our wrists, in our living rooms, in our kitchens, and in our automobiles. Getting the basics right is of utmost importance before we start expanding.

Android 7.0 for Developers: New Features, Performance Upgrades & Other Stuff You Won’t Care About


Google formally announced Android 7.0 Nougat a few weeks ago, but as usual, you’ll have to wait. Most users won’t get their over-the-air (OTA) updates until early next year. Many others will receive them a week from never, as some device vendors simply don’t bother.

This may sound like a snarky pet peeve of mine, but Android fragmentation is no joke; it’s been a serious headache for users and developers for years. Android 7.0 won’t solve that issue, which is a shame because it enables a number of new features and performance improvements that users would surely enjoy.

Developers shouldn’t get their hopes up, however; there aren’t any game-changers here. Let’s look at the key tweaks under Android’s hood and the new opportunities they present, from most to least impactful.

  1. New JIT compiler, complementing ART’s existing AOT compiler
  2. Multi-window support
  3. Support for Vulkan API
  4. Direct boot
  5. Direct reply and bundled notifications
  6. Daydream virtual reality (VR) mode
  7. UI, accessibility tweaks, and background optimization

This is obviously not a comprehensive list of all new features; I settled on the top seven. You can get an in-depth overview of Android 7.0 if you head over to Google’s developer paradise. I will spare you the unnecessary fluff and provide you with useful info in a condensed, easy-to-digest form.

Powered by Blogger.