A report on the state of ipfs on iOS.
- Dominant language
- Go
- Stars
- 17.1k
- Forks
- 3.2k
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 11
Description
On this repo:
EDIT: new repo: https://github.com/seclorum/ios-go-ipfs
.. is now a functioning iOS project set up to allow Go and Objective-C/frameworks to co-exist - i.e. Go on iOS. It works well enough to host a web server (from Go side) and do basic data interchange between Obj-C/Go runtimes. Just the basics, but functional so far for a basic set of Go packages.
The ipfsios XCode project is also set up to include and build a test ipfs daemon, with the intention that "ipfs daemon" is done alongside good ol' ApplicationDelegate at startup, and PeerID's are a-happenin' .. although this is currently in broken state and unrealistic at present - some things are simply missing in the goios syscall department, it seems. But at least the framework is there to include ipfs on iOS as a target.
So far the list of things to fix seems promising - but I'd be happy if you ipfs guys could take a look at the build output in this issue and make comments? End-goal, ipfs on iOS! :)
https://github.com/seclorum/ipfs-on-ios/issues/1
Contributor guide
Research direction
Start by reviewing the linked ios-go-ipfs repository and the ipfs-on-ios issue, then inspect the ipfsios Xcode project and its build output. Establish which missing Go-on-iOS syscalls block the daemon and define a scoped acceptance test for running it alongside ApplicationDelegate; this issue does not specify a concrete change or done state.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, ios, objective-c
- Domain
- mobile-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100