English (United Kingdom)

https://curated-unify.zendy.io/wp-json/zendy-region/v1/featured_content/oa?rat=en

https://curated-unify.zendy.io/wp-json/zendy-region/v1/highlighted_journal/

Global: Zendy Tools annual

Presents the keyphrase highlighting as premium feature

Keyphrase Highlighting

Presents the summarisation as premium feature

Summarisation

Insights

Presents the pdf analysis as premium feature

PDF Analysis

Presents the zaia usage as premium feature

ZAIA

Global: Zendy Tools monthly

Global: Zendy Plus monthly

Presents the access of premium content as premium feature

Premium Content

Global: Zendy Plus annual

Global: Zendy Free Plan

Technical debt describes situations where developers write less-than-optimalcode to meet project milestones. However, this debt accumulation often resultsin future developer effort to live with or fix these quality issues. To bettermanage this debt, developers may document their sub-optimal code as comments inthe code (i.e., self-admitted technical debt or SATD). While prior research hasinvestigated the occurrence and characteristics of SATD, this research hasprimarily focused on non-mobile systems. With millions of mobile applications(apps) in multiple genres available for end-users, there is a lack of researchon sub-optimal code developers intentionally implement in mobile apps.  In this study, we examine the occurrence and characteristics of SATD in15,614 open-source Android apps. Our findings show that even though such appscontain occurrences of SATD, the volume per app (a median of 4) is lower thanin non-mobile systems, with most debt categorized as Code Debt. Additionally,we identify typical elements in an app that are prone to intentionalsub-optimal implementations. We envision our findings supporting researchersand tool vendors with building tools and techniques to support app developerswith app maintenance.

An Exploratory Study on the Occurrence of Self-Admitted Technical Debt in Android Apps