Pocket code build variants

Kirshan Kumar Luhana

Research output: Chapter in Book/Report/Conference proceedingConference contributionResearchpeer-review

Abstract

This case study is about Pocket Code's build variants. Pocket Code is a free and open source integrated development environment (IDE) for the brick based visual programming language Catrobat. It is released in various flavors for different partners and projects (e.g., Create@School, Phiro and Standalone). All flavors use the same code base but slightly differ in design and functionality. If different flavors are maintained as separate projects, all projects require proper maintenance. Any feature introduced or updated in one project must be ported to all others, for that they dont diverge. With an increase in the number of flavors, efforts to maintain will also increase which renders the project unmaintainable. If all flavors are maintained in one project, it is challenging to release more than one version of an application with a different set of functionalities and different user interface (UI) enhancements. In this paper, Pocket Code's different build variants are discussed particularly the standalone build variant. To build a standalone version of any app hosted on the Pocket Code sharing platform, the user has to trigger the build via the web interface on the remote Pocket Code server. Resource files and app configuration are generated based on user input. This paper can be of interest to organizations dealing with dynamic build variants triggered by external actors.

Original languageEnglish
Title of host publication2018 IEEE International Conference on Innovative Research and Development, ICIRD 2018
PublisherInstitute of Electrical and Electronics Engineers
Pages1-6
Number of pages6
ISBN (Electronic)9781538656969
DOIs
Publication statusPublished - 8 Jun 2018
Event2018 IEEE International Conference on Innovative Research and Development, ICIRD 2018 - Bangkok, Thailand
Duration: 11 May 201812 May 2018

Conference

Conference2018 IEEE International Conference on Innovative Research and Development, ICIRD 2018
CountryThailand
CityBangkok
Period11/05/1812/05/18

Fingerprint

Flavors
Application programs
Visual Languages
Brick
Computer programming languages
User interfaces
Interfaces (computer)
Diverge
Trigger
Open Source
Servers
User Interface
Programming Languages
Sharing
Maintenance
Server
Enhancement
Configuration
Resources
Functionality

Keywords

  • Android Build variant
  • Dynamic Software Product Lines (DSPLs)
  • Pocket Code

ASJC Scopus subject areas

  • Artificial Intelligence
  • Computer Networks and Communications
  • Computer Science Applications
  • Information Systems and Management
  • Safety, Risk, Reliability and Quality
  • Media Technology
  • Control and Optimization
  • Metals and Alloys

Cite this

Luhana, K. K. (2018). Pocket code build variants. In 2018 IEEE International Conference on Innovative Research and Development, ICIRD 2018 (pp. 1-6). Institute of Electrical and Electronics Engineers. https://doi.org/10.1109/ICIRD.2018.8376329

Pocket code build variants. / Luhana, Kirshan Kumar.

2018 IEEE International Conference on Innovative Research and Development, ICIRD 2018. Institute of Electrical and Electronics Engineers, 2018. p. 1-6.

Research output: Chapter in Book/Report/Conference proceedingConference contributionResearchpeer-review

Luhana, KK 2018, Pocket code build variants. in 2018 IEEE International Conference on Innovative Research and Development, ICIRD 2018. Institute of Electrical and Electronics Engineers, pp. 1-6, 2018 IEEE International Conference on Innovative Research and Development, ICIRD 2018, Bangkok, Thailand, 11/05/18. https://doi.org/10.1109/ICIRD.2018.8376329
Luhana KK. Pocket code build variants. In 2018 IEEE International Conference on Innovative Research and Development, ICIRD 2018. Institute of Electrical and Electronics Engineers. 2018. p. 1-6 https://doi.org/10.1109/ICIRD.2018.8376329
Luhana, Kirshan Kumar. / Pocket code build variants. 2018 IEEE International Conference on Innovative Research and Development, ICIRD 2018. Institute of Electrical and Electronics Engineers, 2018. pp. 1-6
@inproceedings{2c6356d9f8b94179b935a3ec42c9beb0,
title = "Pocket code build variants",
abstract = "This case study is about Pocket Code's build variants. Pocket Code is a free and open source integrated development environment (IDE) for the brick based visual programming language Catrobat. It is released in various flavors for different partners and projects (e.g., Create@School, Phiro and Standalone). All flavors use the same code base but slightly differ in design and functionality. If different flavors are maintained as separate projects, all projects require proper maintenance. Any feature introduced or updated in one project must be ported to all others, for that they dont diverge. With an increase in the number of flavors, efforts to maintain will also increase which renders the project unmaintainable. If all flavors are maintained in one project, it is challenging to release more than one version of an application with a different set of functionalities and different user interface (UI) enhancements. In this paper, Pocket Code's different build variants are discussed particularly the standalone build variant. To build a standalone version of any app hosted on the Pocket Code sharing platform, the user has to trigger the build via the web interface on the remote Pocket Code server. Resource files and app configuration are generated based on user input. This paper can be of interest to organizations dealing with dynamic build variants triggered by external actors.",
keywords = "Android Build variant, Dynamic Software Product Lines (DSPLs), Pocket Code",
author = "Luhana, {Kirshan Kumar}",
year = "2018",
month = "6",
day = "8",
doi = "10.1109/ICIRD.2018.8376329",
language = "English",
pages = "1--6",
booktitle = "2018 IEEE International Conference on Innovative Research and Development, ICIRD 2018",
publisher = "Institute of Electrical and Electronics Engineers",
address = "United States",

}

TY - GEN

T1 - Pocket code build variants

AU - Luhana, Kirshan Kumar

PY - 2018/6/8

Y1 - 2018/6/8

N2 - This case study is about Pocket Code's build variants. Pocket Code is a free and open source integrated development environment (IDE) for the brick based visual programming language Catrobat. It is released in various flavors for different partners and projects (e.g., Create@School, Phiro and Standalone). All flavors use the same code base but slightly differ in design and functionality. If different flavors are maintained as separate projects, all projects require proper maintenance. Any feature introduced or updated in one project must be ported to all others, for that they dont diverge. With an increase in the number of flavors, efforts to maintain will also increase which renders the project unmaintainable. If all flavors are maintained in one project, it is challenging to release more than one version of an application with a different set of functionalities and different user interface (UI) enhancements. In this paper, Pocket Code's different build variants are discussed particularly the standalone build variant. To build a standalone version of any app hosted on the Pocket Code sharing platform, the user has to trigger the build via the web interface on the remote Pocket Code server. Resource files and app configuration are generated based on user input. This paper can be of interest to organizations dealing with dynamic build variants triggered by external actors.

AB - This case study is about Pocket Code's build variants. Pocket Code is a free and open source integrated development environment (IDE) for the brick based visual programming language Catrobat. It is released in various flavors for different partners and projects (e.g., Create@School, Phiro and Standalone). All flavors use the same code base but slightly differ in design and functionality. If different flavors are maintained as separate projects, all projects require proper maintenance. Any feature introduced or updated in one project must be ported to all others, for that they dont diverge. With an increase in the number of flavors, efforts to maintain will also increase which renders the project unmaintainable. If all flavors are maintained in one project, it is challenging to release more than one version of an application with a different set of functionalities and different user interface (UI) enhancements. In this paper, Pocket Code's different build variants are discussed particularly the standalone build variant. To build a standalone version of any app hosted on the Pocket Code sharing platform, the user has to trigger the build via the web interface on the remote Pocket Code server. Resource files and app configuration are generated based on user input. This paper can be of interest to organizations dealing with dynamic build variants triggered by external actors.

KW - Android Build variant

KW - Dynamic Software Product Lines (DSPLs)

KW - Pocket Code

UR - http://www.scopus.com/inward/record.url?scp=85049911426&partnerID=8YFLogxK

U2 - 10.1109/ICIRD.2018.8376329

DO - 10.1109/ICIRD.2018.8376329

M3 - Conference contribution

SP - 1

EP - 6

BT - 2018 IEEE International Conference on Innovative Research and Development, ICIRD 2018

PB - Institute of Electrical and Electronics Engineers

ER -