We built a library (SDK) for iOS. The source code of the library is closed (proprietary). The output we want to release is iOS frameworks, API documentation, setup guide, license file but NO source code.
We are discussing different ways to release it to the public.
1) One way is to create a public git repository hosted in Github and push all the output in it.
2) Another way is to host these files on our own server.
Is there any benefit of hosting it on GitHub over hosting it on our own servers? I know git is to manage source files but in this case, there is no source file that we want to publish, it is just the output. Is there any general rule to release iOS close source SDKs?. I tried many IOS and Git training resources to find a solution for this. Unluckily I couldn't able to. I am inclined more towards hosting the SDK (as zips) in our own server. I believe it is always the latest SDK you market on your website and not the older SDK.
댓글 1개
게시글 목록
| 번호 | 제목 |
|---|---|
| 2136 |
Android
안드로이드 웹뷰어
2
|
| 2131 | |
| 2122 | |
| 2112 |
Hybrid
최근 svelte로 만든 하이브리드앱들
5
|
| 2108 | |
| 2106 | |
| 2102 | |
| 2099 |
Hybrid
캐패시터 (Ionic Capacitor)
|
| 2093 |
Hybrid
vue native 어떤가여 ㅋㅋ
7
|
| 2084 |
Hybrid
플러터와 네이티브 어플
3
|
| 2080 | |
| 2077 | |
| 2070 | |
| 2068 |
IOS
넷플릭스앱
|
| 2067 |
기타
C++
|
| 2065 | |
| 2064 | |
| 2063 | |
| 2062 | |
| 2059 | |
| 2055 |
Android
안드로이드 앱 퍼블리셔 / 운영팀 or 사업부
|
| 2053 | |
| 2047 | |
| 2044 | |
| 2037 | |
| 2036 | |
| 2033 | |
| 2027 | |
| 2026 | |
| 2025 |
기타
Flutter 2
|
댓글 작성
댓글을 작성하시려면 로그인이 필요합니다.
로그인하기