Understanding Developer Pain Points in Federated Learning: Insights from Stack Overflow and GitHub

📅 2026-07-21
📈 Citations: 0
Influential: 0
📄 PDF
🤖 AI Summary
This study addresses the practical challenges developers encounter in deploying and iterating federated learning systems, including distributed execution, framework evolution, and privacy compliance, which often manifest as environment configuration issues, API instability, and training unreliability. Through the first large-scale comparative analysis of 495 Stack Overflow posts and 9,116 GitHub issues, the authors employ BERTopic-based topic modeling, intent classification, and resolution metrics to systematically identify nine core problem categories on Q&A platforms and thirteen on code repositories. The findings highlight persistent difficulties such as environment compatibility, non-IID data training, and integration of privacy-preserving mechanisms, while revealing a strong developer demand for actionable guidance. These insights provide empirical grounding and concrete recommendations for improving federated learning frameworks and their documentation.
📝 Abstract
Federated Learning (FL) enables collaborative model training without centralizing raw data, but building and operating FL systems remains difficult due to distributed execution, rapidly evolving frameworks, and privacy and governance requirements. In this paper, we present an empirical study of FL developer challenges by independently analyzing 495 Stack Overflow posts and 9,116 GitHub issues and pull requests from 92 FL-related projects. Using BERTopic-based topic modeling and difficulty indicators such as unresolved rates and median resolution time, we characterize recurring problem areas and compare how they manifest across the two support platforms, Stack Overflow and GitHub. Our analysis surfaces nine dominant Stack Overflow topics and thirteen GitHub topics, with persistent difficulties concentrated in environment setup and dependency compatibility, API breakages and migration, training instability under non-IID data, evaluation and metric correctness, and the integration of privacy-preserving mechanisms. We also categorize posts by question intent to understand the kinds of help developers seek; this intent analysis shows that "How"-type questions dominate, reflecting strong demand for procedural guidance. Several topics, such as "TFF Installation and Environment Compatibility" and "Federated Feature Engineering and SecureBoost Issues," exhibit high unresolved rates and long resolution times, suggesting shortcomings in tooling, documentation, and debugging support. Based on these findings, we provide actionable implications for FL framework designers, documentation authors, and educators. Although our results are constrained to public discussions and a subset of widely discussed frameworks, the study offers a scalable method for continuously monitoring developer pain points and improving the usability, reliability, and deployability of FL systems.
Problem

Research questions and friction points this paper is trying to address.

Federated Learning
Developer Challenges
Non-IID Data
Privacy-Preserving Mechanisms
API Breakages
Innovation

Methods, ideas, or system contributions that make the work stand out.

Federated Learning
Developer Pain Points
Empirical Study
BERTopic
Non-IID Data
S
Sahand Saed
Department of Computer Science, University of Saskatchewan, Saskatoon, S7N 5A2, Saskatchewan, Canada
K
Khairul Alam
Department of Computer Science, University of Saskatchewan, Saskatoon, S7N 5A2, Saskatchewan, Canada
Banani Roy
Banani Roy
University of Saskatchewan
Interactive Software EngineeringBig Data AnalyticsSoftware MaintenanceScientific Workflows