drukscode/drukscode-v2
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
drukscode-v2/docs/guide/app-actions/export-apk.md
OpenCode AI e9899d2e6d
Some checks failed
Android CI Build / check (push) Has been cancelled
Details
Android CI Build / package-apks (push) Has been cancelled
Details
Docs Deploy / build (push) Has been cancelled
Details
Module Market Check / Validate modules/ (push) Has been cancelled
Details
Module Market Publish / Generate submissions.json (push) Has been cancelled
Details
Docs Deploy / deploy (push) Has been cancelled
Details
Initial DruksCode V2: fresh fork of web-to-app (f3b488e) with DruksCode identity 
- Package rename com.webtoapp -> br.com.drukstech.codeapp
- Product rename WebToApp/web-to-app -> DruksCode/drukscode
- Design system Wta* -> Dkc*
- applicationId br.com.drukstech.codeapp (.play for gplay flavor)
- rootProject.name DruksCode
- Fresh git history (upstream kept as remote for sync)
2026-09-12 02:42:02 +02:00

690 B
Raw Permalink Blame History

Export

Exports the app as a reusable project template you can import on another device. Tap ⋮ on an app card, then Export.

How it works

  • DruksCode packages the app's configuration (and content) into a portable template.
  • On success, the output path is reported.

Export vs Build vs Share

Action Produces
Export A reusable project template (re-importable)
Build APK An installable, signed APK
Share APK A built APK sent via the share sheet

Notes

  • Use Export to move an app's definition between devices; use Build/Share to distribute an installable APK.