Open tests, a reproducible example and bilingual guides for an existing Expo / React Native package.
I maintain expo-alphatab, an MIT-licensed package that brings offline music notation and playback to Expo / React Native applications. It packages the integration I built for Fretbox, my released iOS guitar-tab app. Developers can reuse the wrapper instead of separately solving asset loading and communication between a native app and the alphaTab browser engine. I am seeking USD 1,500–3,000 to improve the public package, tests and documentation. The grant would pay for work released openly; it would not fund proprietary Fretbox features. Source: https://github.com/juapperez/expo-alphatab .
What are this project's goals? How will you achieve them?
With the full USD 3,000, I propose a twelve-week maintenance project starting after funding: (1) expand tests around missing assets, malformed bridge messages and error handling; (2) publish a small reproducible Expo example using original or permissively licensed example music; (3) check installation and playback on iOS and investigate Android behavior, documenting any unresolved failures; and (4) publish English and Spanish installation and troubleshooting guides, a compatibility record and a versioned release. The minimum USD 1,500 would fund a six-week version focused on bridge and asset-error tests plus bilingual setup and troubleshooting documentation. The example app and Android investigation would be deferred in the minimum scope. Dates would be agreed after funding.
How will you know it worked?
I will publish the source changes, reproducible test commands and results, documented environment versions, release notes and links to the completed guides. For the full scope, the example will include instructions to reproduce installation and playback; Android results will be reported even if they reveal a limitation rather than a working configuration. The existing package has seven passing protocol tests and an iOS integration in Fretbox. Broad external adoption and independently measured educational benefits are not established. This project aims to reduce setup and maintenance work for developers of music-learning tools; I will not treat downloads as proof of learning outcomes.
How will this funding be used?
The full budget is 100 hours of my implementation and documentation work at USD 30/hour: 35 hours for tests and error handling (USD 1,050), 25 hours for the reproducible example and compatibility checks (USD 750), 20 hours for the Android investigation (USD 600), and 20 hours for bilingual documentation and the release (USD 600). Total: USD 3,000. The minimum budget is 50 hours at the same rate: 30 hours for tests and error handling (USD 900) and 20 hours for documentation and the release (USD 600), totaling USD 1,500. These are proposed gross compensation estimates, including my applicable taxes, not already incurred costs. No travel, equipment purchase or third-party contractor is budgeted. If the net award differs, I will agree the deliverables and budget with the funder before starting.
Who is on your team? What's your track record on similar projects?
I am Juan Pablo Pérez Vélez, a software developer and Chemical Engineering undergraduate at Universidad Nacional de Colombia in Medellín. I am applying independently and am the author and primary maintainer of expo-alphatab. I released the public package in October 2026, after using the integration in Fretbox on iOS. I am the proposed sole contributor for this grant. The upstream alphaTab maintainers are separate and are not represented as members of my team. The wrapper remains MIT-licensed; the engine, Bravura font and sonivox soundfont retain their separate licenses.
What are the most likely causes and outcomes if this project fails?
WebView file access or upstream changes may prevent an Android configuration from working, and a small package may attract few outside users even with better documentation. Compatibility work can also take longer than estimated. I will preserve the useful test and documentation improvements, publish the limitations and negative results, and agree any material scope changes with the funder. The deliverable is inspectable maintenance work, not a promise of adoption or universal platform support.
How much money have you raised in the last 12 months, and from where?
For expo-alphatab, which I released in October 2026, I have received USD 0 in grant or sponsorship funding and have no organizational support. A USD 500 maintenance microgrant request to evm.capital and a Sequoia Open Source Fellowship application are pending. Sequoia would support a broader maintenance roadmap and living expenses; the amount is not specified. This Manifund request is an alternative source for the work described above. If another application is funded, I will disclose it and reduce or separate overlapping work before accepting funds. The same work or hours will not be charged to two awards.
There are no bids on this project.
Comments
No comments yet. Sign in to create one!