mattrobenolt / mattrobenolt/appify
Standalone applications
Nobody has claimed this yet.
- Dominant language
- Zig
- Stars
- 151
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
Currently, appify lacks a mode to bundle the target TUI program and its dependencies into the .app package. This would create a standalone application, making it easier to distribute.
Discussion:
1. Should we bundle the program’s dynamic library dependencies? If so, how do we identify which libraries need to be included?
2. Some TUI programs default to storing data in the current working directory, whereas .app bundles are expected to store data in standard system directories. Should appify be responsible for handling this discrepancy?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue does not identify files, tests, or an entry point to inspect. First resolve whether dynamic-library bundling and working-directory data handling are in scope; done would be a standalone .app containing the TUI program and its required dependencies.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos, zig
- Domain
- cli, desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100