Mobile phishing attacks, such as mimic mobile browser pages, masquerade as legitimate
applications by leveraging repackaging or clone techniques, have caused varied yet …

Existing approaches for program debloating often use a usage profile, typically provided as
a set of inputs, for identifying the features of a program to be preserved. Specifically, given a …

Existing programming practices for building Android apps mainly follow the “one-size-fits-all”
strategy to include lots of functions and adapt to most types of devices. However, this …

Programs are becoming increasingly complex and typically contain an abundance of
unneeded features, which can degrade the performance and security of the software …

Software systems execute tasks that depend on different types of resources. However, the
variability of resources may interfere with the ability of software systems to execute important …

The size of Android applications is getting larger to fulfill the requirements of various users.
However, not all the features of the applications are needed and desired by a specific user …

Current mobile applications (apps) have become increasingly complicated with increasing
features that are represented on the graphical user interface associated with application …

Today's Android users face a security dilemma: they want to grant permissions to apps for
enjoying more abundant functionalities, but also worry that the apps may abuse these …

Android apps typically include many functionalities that not all users require. These result in
software bloat that increases possible attack surface and app size. Common functionalities …

Existing source code debloaters fall short due to low scalability and high runtime overhead
when applied in dynamic cloud settings, where instances are spun up on the fly. To address …