MSECO-DEV: Application Development Process in Mobile Software Ecosystems

Abstract

In a Mobile Software Ecosystem (MSECO), the central organization (keystone), must restructure processes to aid external developers to produce mobile applications. The external developer helps the keystone to reach goals, such as growing number of mobile applications. However, there is no process in this context to support developers in the development aligned with the keystone's goals. This paper presents MSECO-DEV, a process to support external developers in reaching keystone's goals by developing mobile applications. MSECO-DEV comprises 8 activities, 7 artifacts, 8 recommendations, and 17 practices. Activities, recommendations, and practices were evaluated by 65 Brazilian developers (experts and novices). Such developers acted within the main MSECOs (Android, iOS and Windows Phone) to assess their benefits for the mobile applications development routine. As result, we stated that developers have difficulties to perform marketing activities, as well as to find materials that support development. Practices, activities, and recommendations were also evolved and adjusted for the definition of MSECO-DEV.

Evaluating Processes to Certify Mobile Applications During Developer Relations Activities

“…Within the basic structure provided by the main MSECOs' keystones, there are strategies to support third-party developers, such as development/testing tools and code templates. In this context, there is a class of internal employees who mediate the relationship between a keystone and third-party developers, member of a Developer Relations (DevRel) area, known as developer evangelists [6]. One of the activities of an evangelist is to plan and execute training sessions about the existing technologies of an MSECO platform to increase the number of well-prepared developers as well as the quality of developers' contributions (apps) based on reuse of platforms' functions [29].…”

Tópicos em Sistemas de Informação: Minicursos SBSI 2018

“…A partir da análise das fases e dos elementos que compõem um ECOS, Fontão (2016) identificou três processos (Figura 3.3): (1) Orquestraçãoque surge da interação entre a organização central e o evangelista, uma vez que este se baseia nas diretrizes do ECOS para executar atividades de suporte;…”

A Developer Relations (DevRel) model to govern developers in Software Ecosystems

“…12 Considering this context, there are also internal keystone employees supporting developers in SECO onboard, engagement and recognition. These roles are known as 1,20,21 developer advocate, developer evangelists, partner engineer, and so forth, that compose an internal team called Developer Relations (DevRel). DevRel as the public interface of ecosystem products and platform is responsible for the critical task of translating developer community interactions into trusted relationships with the organization.…”