-
Notifications
You must be signed in to change notification settings - Fork 7
Development Ideas & Areas of Interest
This page collects some of the development ideas, technical topics, and areas of interest that have been discussed around TreeFrogUI.
The purpose of this page is not to define a strict roadmap, establish priorities, or promise that any particular feature will be implemented.
Instead, it serves as a reference for topics that have come up in discussions and that may be worth exploring as the project continues to evolve.
The items listed here should be understood as ideas and areas of interest, not as commitments or scheduled features.
Some of these topics may turn out to be practical, while others may be limited by hardware, software, available development time, or technical complexity.
The following areas have been mentioned as potentially interesting directions for TreeFrogUI:
- USB and Wi-Fi exploration
- PSP emulation
- USB OTG improvements and stabilization
- FrogShell
- Multi-language support
- PlayStation 1 emulator compatibility improvements
These topics are not listed in any particular order of importance.
One area we are interested in learning more about is the connectivity available through the USB ports of supported devices.
Possible areas of exploration include:
- USB devices;
- USB OTG;
- Wi-Fi adapters;
- USB network adapters;
- keyboards;
- USB storage;
- USB hubs;
- networking;
- file transfer;
- development and debugging tools.
The main idea would be to better understand what is possible with the existing hardware and software environment.
Some handhelds may behave differently depending on:
- USB controller;
- kernel support;
- available drivers;
- power requirements;
- hardware revision;
- OTG implementation.
It could be useful to document which devices and adapters work reliably and whether any of these capabilities could eventually be integrated into TreeFrogUI.
Another topic that has been mentioned is the possibility of PlayStation Portable emulation.
PSP would be an interesting platform to experiment with, although the hardware used by TreeFrogUI devices may make this technically challenging.
Things that could be investigated include:
- available PSP emulators;
- whether they can run on the target architecture;
- CPU requirements;
- memory requirements;
- graphics performance;
- audio performance;
- input support;
- game compatibility;
- possible optimization options.
The goal of this exploration would initially be to understand what is technically possible.
Even if full PSP support is not realistic, testing may help identify whether some games or emulator configurations are usable.
TreeFrogUI already has support for using USB OTG storage in some scenarios.
It may be useful to continue testing and improving this functionality.
Areas worth investigating include:
- USB device detection;
- automatic mounting;
- initialization delays;
- safe removal;
- unexpected disconnections;
- different USB adapters;
- USB hubs;
- storage compatibility;
- filesystem behavior;
- differences between handheld models.
Because USB hardware can vary significantly, community testing with different combinations of devices and adapters could be especially useful.
The intention here would be to make OTG functionality more predictable and better documented where possible.
We have also discussed the idea of a lightweight developer-oriented utility tentatively called FrogShell.
The general idea would be to provide additional tools for advanced users, contributors, and developers without affecting the normal TreeFrogUI experience.
Possible features could include:
A simple local terminal could be useful for:
- inspecting files;
- viewing system information;
- checking mounted devices;
- reading logs;
- testing commands;
- diagnosing problems.
Another idea would be allowing scripts stored on the SD card to be executed from a dedicated interface.
Possible uses might include:
- diagnostics;
- maintenance tools;
- development utilities;
- configuration scripts;
- experimental features.
FrogShell could potentially be connected to an optional Developer Mode.
This mode could expose additional functionality such as:
- debug information;
- extended logging;
- system information;
- hardware information;
- storage information;
- script execution;
- experimental options.
The idea would be for these features to remain hidden or disabled by default, so that normal users continue to have a simple interface.
Developer-oriented tools would only appear when intentionally enabled.
Adding support for multiple interface languages is another area we are interested in exploring.
A localization system could make TreeFrogUI easier to use for a wider community.
Possible languages could eventually include:
- English
- Spanish
- Portuguese
- French
- German
- and others contributed by the community.
A possible implementation would involve moving interface text into separate language files.
For example:
languages/
โโโ en.json
โโโ es.json
โโโ pt.json
โโโ fr.json
โโโ de.json
The exact format has not been defined and may be different depending on what works best for TreeFrogUI.
Some technical considerations would include:
- UTF-8 support;
- accented characters;
- fonts;
- translated strings of different lengths;
- menu layouts;
- missing translations;
- fallback languages.
English could remain available as a fallback when a translation is missing.
If localization support is implemented, translations could also become an area where community contributions would be particularly valuable.
PlayStation 1 compatibility is another topic we would like to continue investigating.
Some games may behave differently depending on:
- emulator core;
- BIOS;
- ROM format;
- region;
- graphics behavior;
- audio behavior;
- timing;
- game-specific characteristics.
Possible issues worth investigating include:
- games that fail to launch;
- crashes;
- graphical glitches;
- audio problems;
- performance problems;
- controller behavior;
- multi-disc games;
-
.cue/.bincompatibility; - save compatibility.
It could also be useful to compare different PS1 emulators or cores and determine whether certain games perform better with specific configurations.
Over time, this information could potentially become a compatibility reference containing:
- tested games;
- known issues;
- recommended cores;
- recommended settings;
- known workarounds.
Community testing would be very useful for building this information.
As these ideas are explored, testing may be useful in areas such as:
- PS1 game compatibility;
- USB OTG behavior;
- USB peripherals;
- Wi-Fi adapters;
- PSP emulator experiments;
- different hardware revisions;
- FrogShell tools;
- localization and fonts.
When sharing test results, information such as the following can make reports much more useful:
Device:
Hardware revision:
TreeFrogUI version:
Feature being tested:
Peripheral / adapter:
Game:
ROM format:
BIOS:
Expected result:
Actual result:
Additional notes:
Logs can also be useful when available.
These ideas are intentionally open-ended.
Feedback from users and contributors can help determine:
- whether a feature is useful;
- whether a feature works across different devices;
- what technical problems exist;
- which hardware limitations need to be considered;
- whether alternative approaches are available.
Anyone interested in one of these areas is welcome to:
- test;
- investigate;
- document findings;
- report bugs;
- suggest approaches;
- contribute code;
- improve documentation.
Issues and technical discussions can be shared here:
โก๏ธ [TreeFrogUI Issues](https://github.com/tzubertowski/TreeFrogUI/issues)
At the moment, some of the topics that have come up in discussions can be summarized like this:
TreeFrogUI
โ
โโโ Connectivity
โ โโโ USB exploration
โ โโโ Wi-Fi exploration
โ โโโ USB OTG improvements
โ
โโโ Emulation
โ โโโ PSP experimentation
โ โโโ PS1 compatibility
โ
โโโ Developer Tools
โ โโโ FrogShell
โ โโโ Terminal
โ โโโ Script execution
โ โโโ Optional Developer Mode
โ
โโโ User Experience
โโโ Multi-language support
This diagram is only intended to organize the topics currently being discussed. It does not represent development priority or implementation order.
This page is expected to change over time.
Topics may be:
- expanded;
- reorganized;
- tested;
- implemented;
- postponed;
- replaced by another approach;
- or removed if they turn out not to be practical.
New ideas may also be added as TreeFrogUI evolves.
This page is best viewed as a collection of possible directions and technical interests, rather than a fixed development plan.
๐ธ TreeFrogUI continues to evolve through experimentation, testing, discussion, and contributions from the community.