Find open source projects actively accepting contributors. Search repositories, filter by program milestones, difficulty tags, or tech stack.
Use our Orbit AI Matcher to find out! Get instant matching scores based on your developer skills, preferred frameworks, and contribution experience.
Convert your selected open-source project into a winning GSoC, LFX, or Outreachy application using Proposal Studio.
<p>The color interface in App Inventor deals with multiple different formats, this leads to confusion for the user while switching from one part of App Inventor to the other. This project will make additions to GUI Color Picker in designer, the blocks in the color drawer, add a mechanism to detect blocks that return a color, and add an option to see the visual representation of a color in the Blocks editor. Our objective is to make a user interface for colors that solve the problems expressed by the community, one that allows the community to interact with the colors in app inventor in a more efficient, consistent, and beginner-friendly way.</p>
This proposal aims to implement the Menu, Sidebar, and Floating Action Button (FAB) components in iOS for MIT App Inventor, ensuring feature parity with Android as introduced in PR #2299. The Menu Component will introduce a dropdown-style menu supporting nested items, icons, and keyboard navigation. The Sidebar Component will provide a sliding navigation panel with swipe gestures, tap-to-close functionality, and essential navigation links like Home, Profile, Settings, and Logout. The Floating Action Button (FAB) will be a circular, floating button positioned at the bottom-right, supporting custom actions, animations, and a shadow effect for a modern UI experience. A key aspect of this project is ensuring feature parity with Android, maintaining UI/UX consistency across both platforms. I chose this project because it bridges the gap between iOS and Android, ensuring that MIT App Inventor provides a seamless cross-platform experience. It also enhances user experience by introducing smooth, intuitive navigation and interactions, making iOS-built apps more functional and engaging. Additionally, this project will expand MIT App Inventor’s capabilities by adding essential missing features, making the platform more versatile and user-friendly. The estimated timeline for this project is 175 hours, covering implementation, testing, and final integration. Upon completion, this update will significantly enhance MIT App Inventor’s iOS version, making it a fully-featured, cross-platform development tool that aligns with modern app-building standards.
<p>This is the new feature added in MIT APP INVENTOR which allows users not to permanently delete the project once they click the Delete button intentionally or unintentionally. Rather it moves the deleted projects to Trash tab and once user makes up his mind he can go to trash tab and delete the project permanently.</p>
<p>With this project, we will be able to provide one of the most sought out feature i.e menu options in applications developed from App Inventor. In current days android applications, menu options is one of the critical feature to provide your users, easy access to some of the basic features such as Search, Log out, About us, FAQ’s, Settings, Help, etc. As hundreds of applications has been developed using App Inventor on the daily basis, it would be high time to provide the menu options to App Inventor community.</p>
This project focuses on redesigning the ListView component in MIT App Inventor to address key architectural, performance, and cross-platform consistency issues. Currently, the component suffers from inefficient full adapter rebuilds, lack of a structured data model, and inconsistencies between Android and iOS implementations. These issues lead to performance overhead, unreliable behavior, and poor developer experience, especially for beginners. To solve this, the project introduces a structured, phased approach: Core Refactor (Reliability): Introduce a dedicated ListDataModel to manage items, selection state, and filtering. This eliminates full adapter reconstruction and enables efficient incremental updates. Cross-Platform Consistency (Continuity): Establish a behavioral contract and parity tracking system to systematically align Android and iOS implementations, fixing missing features, type mismatches, and runtime inconsistencies. API Expansion (Extensibility): Add block-level operations such as AddElement, RemoveElement, UpdateElement, ScrollToElement, and SelectionElements, along with full multi-select support. User Experience Improvements: Enhance the Designer with a UIBinder-based list editor, keyboard navigation, and introduce a swipeable (carousel-style) layout for modern UI interaction. Deliverables Modular ListDataModel architecture with incremental update support Eliminated full adapter rebuilds and improved performance Android–iOS feature parity with validated behavior New block-level APIs and multi-select functionality Redesigned Designer editor with improved usability Swipeable ListView layout implementation Comprehensive testing, documentation, and backward compatibility assurance This project aims to make ListView more scalable, consistent, and beginner-friendly, while establishing a maintainable foundation for future enhancements.
The main point is to create an abstract class in both Swift and Java, shared among all AI components, which will contain all the necessary functions for such components. This abstract class will then be inherited by the ImageClassifier and AudioClassifier classes, allowing them to perform correct classification, especially thanks to asynchronous operations, utilizing AsyncTask in Java and GCD in Swift, respectively.
This proposal aims to enhance MIT App Inventor by developing artificial intelligence (AI) components for iOS platforms. By re-implementing existing AI features, the project seeks to democratize AI development and empower users to seamlessly integrate AI functionalities into their mobile applications. The deliverables include designing and implementing these components, integrating them into the MIT App Inventor platform, providing comprehensive documentation and tutorials, and conducting thorough testing for reliability and performance. Ultimately, this endeavor strives to foster innovation and creativity in mobile app development while making AI accessible to a broader audience.
This project is to enable the selection of multiple blocks at the same time and allow moving and doing actions on multiple blocks on Blockly. This behaviour is pretty much the same as when you try to manage your files on your Operating System, and you can drag a rectangle to select multiple files, then moving them around, copying, deleting. The design is that the Blocks multi-select feature will be only functional when you hold the Shift key, so that users can still drag the workspace when not. Users can simply click on the blocks to select or unselect them, or drag a rectangle to select a set of them at the same time. A button would also be added to enable multi-selection feature in case users are unable to access the keyboard. It sounds like a little bit easy, but actually, I would say that it's not. Multiple selections can become a crazy-complex feature when you start thinking about the details. When dragging two blocks, you have to think about how the connections will work. When you right-click on multiple selections, you also have to make sure that those options apply to all blocks. And the touch screen problem would also need to be addressed. The feature request (https://github.com/google/blockly-samples/issues/267) has remained open on the GitHub Issues for 6 years, but it's still in the discussion phase and far from the beginning of Implementation there. So I hope we can implement that during GSoC 2022 if possible.
App Inventor 2 allows users to extend its functionality by using third-party extensions. Extensions are similar to built-in components, they can do everything from showing UI elements on the screen to performing tasks in the background. However, unlike built-in components, extensions are unable to have a mock preview in App Inventor's designer. The goal of this project is to make it possible for extension developers to be able to create mock previews for their extensions using web technologies, while also making sure that the security and stability of App Inventor is not compromised because of untrusted third-party code.
<p>This project aims to improvise ListView in App Inventor. It was one of the most demanded improvements from users. Idea - Adding custom layouts to ListView. Expected Outcome - 1) Users will be able to select one of the pre-defined ListView layouts and use it in their applications. 2) Users will be able to create any custom row of ListView if it is not present in the pre-defined set of layouts.</p>
<p>Each operating system has its own "packages" that allow installing different applications to extend the features in the device. Android is not an exception, and their package type is the .apk file type (Android Application Package). This file has been present in Android since the very beginnings, allowing the development of several applications.<br> And App Inventor has the ability to build the app projects into those .apk files, as it is an Android app creator.</p> <p>Google, as the owner of Android, always tries to optimize its environment by protecting the users and enhancing the development ecosystem, among other things. So, they wanted to make a change. In Google I/O 2018, Google introduced the .aab file format (Android App Bundle).<br> This new format is being used by Google Play Store, and Google is encouraging everyone to use it when distributing apps.</p> <p>This project proposal intends to bring the option of exporting app projects in MIT App Inventor as .aab files, which make their distribution more straightforward in Google Play Store.<br> Moreover, if App Inventor had support for .aab files, it would be possible to make use of the App Signing by Google Play.</p>
<p>A Recycler View component would be created which can display media along with text</p>
<p>The animation portion of the MIT App Inventor, that includes the Canvas, ImageSprite and Ball components, currently has a lot of room for improvement. This project improves the following aspects of the animation portion of MIT App Inventor.</p> <ol> <li>Enabling users to choose a custom origin for image sprites using a drag-able marker. The origin of a sprite is the root of the sprite's coordinate system. All of the interactions of the sprite that may include collisions, positioning etc. is with respect to the origin. This project implements the desired functionality of custom origin in the appinventor system and adds an interactive way, via a drag-able marker, for selecting this origin easily. </li> <li>Improving the algorithm used to detect collisions among sprites. Right now appinventor uses a naive algorithm to detect collisions between sprites. This collision detection does not work correctly for rotated image sprites and they are treated as if they were unrotated. This projects implements the SAT collision detection algorithm that replaces the naive implementation. This helps detect collisions in rotated image sprites and is more extensible.</li> </ol>
App Inventor is becoming increasingly popular among users accessing the platform through mobile phones and handheld devices. In response to this trend, this project aims to implement an enhanced user interface tailored for smaller screens. By leveraging GWT's UiBinder framework, we will introduce flexible interface layouts that adapt to both device type and user preferences, ensuring a seamless and practical experience for mobile users. Deliverables will include optimized interface designs and usability improvements for small-screen devices, aligning with the growing accessibility of handheld technology globally.
<p>A new component of App Inventor for users to display charts on Android device. I discussed the general idea as well as some details of implementation in this proposal.</p>
This project aims to introduce a scalable and maintainable internationalization (i18n) system for applications built using MIT App Inventor. Currently, App Inventor does not provide a structured approach for handling multi-language support, making it difficult for developers to create globally accessible apps. The proposed solution introduces a key-based translation system that decouples user-visible text from UI components. The system integrates across multiple layers of App Inventor, including the Designer, Blockly, runtime, and build system, enabling automatic translation handling in generated applications. Key features include: - Automatic detection of user-visible text from component properties and Blockly blocks - A centralized translation editor for managing multi-language content - Context-based key generation to ensure stability and avoid ambiguity - Runtime translation using JSON for flexibility during development (Companion) - Build-time generation of native Android/iOS resources for efficient production builds The system is designed to be fully backward compatible and supports progressive adoption, allowing existing projects to continue working while enabling developers to gradually migrate to the new translation model. Deliverables include: - A working runtime translation system for App Inventor apps - Integration with Blockly for key-based text handling - Designer-level synchronization and key management - Build-time resource generation for native localization - End-to-end tested implementation with documentation
Functional programming is a programming paradigm where programs are constructed by composing pure functions, avoiding shared state, mutable data, and side effects. Many operators in functional programming are commonly used to make code more concise, and less complex. This proposal hopes to expand the operations in the block editor of MIT App Inventor by implementing new blocks commonly found in functional programming, such as map, reduce, fold, etc.
The primary objective of this project is to enhance the user experience of MIT App Inventor by providing users with information about the availability of components on iOS or Android platforms. To achieve this, proposed changes will be made to the Designer editor code to enable users to determine whether a component is accessible on a particular platform or both. The coverage.json file will be utilized to extract information about the availability of components, which will be represented by iOS or Android icons displayed on the palette items and a text displaying if the component is exclusive to any of the platforms(Android or iOS) on palette Help Popup dialog box. Furthermore, a dialog box will inform users about unsupported components when they connect their devices through the AI companion. The proposed modifications will empower users to make informed decisions when creating their applications, resulting in higher-quality apps that cater to user needs and expectations.
Currently, the properties for the screen1 form contains a number of project project-wide properties such as App Name, Theme and many more. We want these properties separated from the component and maintained on a separate dialog on the designer view.
The project "iOS versions of Android components" aims to develop iOS counterparts of popular Android components that are widely used in mobile app development. The objective is to provide iOS developers with an easier transition between the two platforms, by providing iOS versions of Android components that they are already familiar with. The project will involve identifying and analyzing popular Android components, understanding their functionality and behavior, and then developing their iOS counterparts using Apple's development tools and technologies such as Xcode and Swift. The iOS versions of Android components will be designed to be compatible with the latest versions of iOS, including iOS 14 and higher. The components will be thoroughly tested to ensure compatibility and reliability across different devices and operating system versions. This project will be beneficial to developers who are familiar with Android development and are looking to transition to iOS development. It will also be useful for iOS developers who want to incorporate popular Android components into their iOS apps. Overall, the project aims to improve the ease of transition between Android and iOS development, and ultimately enhance the user experience of mobile apps across both platforms.
While developing apps using MIT App Inventor, students often need help. For this MIT App Inventor has a community where students can reach out for help. While the community is very helpful and makes development easier, it would be even more convenient and time-saving to have a user interface on the app inventor website itself from which users can directly ask questions in the community and project files can be automatically uploaded on community website along with that .
An approach to enhance the functionality of App Inventor by adding the support of augmented reality using Google's expertise AR-Core and OpenGL ES. This will bring Google's augmented reality experience in App Inventor.
The project aims to set up a code coverage metric with additional unit tests to test the GWT client code. We will be using Jacoco a as code coverage metric and writing the Junit tests to unit test the GWT client code.
<p>As a part of my GSoC proposal, I plan to integrate a Menu component in the existing MIT App Inventor. Menus are a common user interface component used to provide the user with a set of actions in an activity. Currently, this can be implemented using a number of buttons and setting their visibility appropriately. Developing a menu this way could be very tedious and complex for the user. Hence having a dedicated component in app inventor would be more convenient.</p>