• Log In
  • Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar
  • Home
  • About
  • Structure
  • Gradebook

ITACS 5211: Introduction to Ethical Hacking

Wade Mackey

November 12, 2018 by Ruby(Qianru) Yang 4 Comments

Along with the launch of a number of new tools and features at its Android Dev Summit 2018, Google has also launched the a new API, called “In-app Updates,” which aims to help developers ensure that users are running the latest and greatest version of their app. Android’s new In-app Updates API doesn’t force or lock out users from the app if they chose not to update it.
Instead, the API has been designed to aggressively inform users about the latest available updates and give them a smooth in-app installation experience without closing the app or opening the Google Play Store.
Google also says that Android developers will have the ability to completely customize the update flow so that it feels like part of your app, which indicates that all apps will not have the same in-app update experience.

https://thehackernews.com/2018/11/android-in-app-updates-api.html

Filed Under: Week 11: SQL Injection Tagged With:

Reader Interactions

Comments

  1. Brock Donnelly says

    November 13, 2018 at 12:19 pm

    This seems like one of those sounded good at first ideas. This API would allow developers to Push their app updates directly through the app. Google already as a issue where malicious apps updates are getting through their app store. How are they going to protect users from malicious code when they are giving developers a backdoor to every phone their app has been installed upon?

    Log in to Reply
  2. Haitao Huang says

    November 14, 2018 at 10:16 am

    This update might significantly improve security in Android devices. Say you shipped your application with a major bug (it happens…) and want to make sure that every user upgrades immediately; you will soon be able to show them a full-screen blocking message that will be displayed when they first start the app again and while the update is applied. That’s obviously only meant for major bugs. The second option allows for more flexibility and allows the user to continue using the app while the update is downloaded. Developers can fully customize these update flows.

    Log in to Reply
    • Ruby(Qianru) Yang says

      December 12, 2018 at 5:58 pm

      Great point Haitao, totally agree with you.

      Log in to Reply
  3. Yingyan Wang says

    November 14, 2018 at 5:53 pm

    Hi Ruby,

    Thank you for sharing this interesting information. It feels like a good and creative idea that “all apps will not have the same in-app update experience”. I think this update gives more flexibility and security for users’ experience. However, it is better for Google to continue monitor this new API to ensure that information of users is protected.

    Log in to Reply

Leave a Reply Cancel reply

You must be logged in to post a comment.

Primary Sidebar

Weekly Discussions

  • Uncategorized (14)
  • Week 01: Overview (7)
  • Week 02: TCP/IP and Network Architecture (18)
  • Week 03: Reconnaisance (17)
  • Week 04: Vulnerability Scanning (19)
  • Week 05: System and User Enumeration (17)
  • Week 06: Sniffers (17)
  • Week 07: NetCat and HellCat (15)
  • Week 08: Social Engineering, Encoding and Encryption (21)
  • Week 09: Malware (14)
  • Week 10: Web Application Hacking (17)
  • Week 11: SQL Injection (15)
  • Week 12: Web Services (25)
  • Week 13: Evasion Techniques (8)
  • Week 14: Review of all topics (15)

Copyright © 2025 · Magazine Pro Theme on Genesis Framework · WordPress · Log in