nullptr/Wallenc
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Улучшение соответсвия

Browse Source
This commit is contained in:
Роман Пытков
2026-05-28 17:23:54 +03:00
parent 5c40687011
commit 0c15c7b786
39 changed files with 161 additions and 204 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
Report/includes/abstract-en.typ
View File

@@ -12,15 +12,11 @@
#pz-front-heading(page-break: false)[Annotation]
#{
set par(first-line-indent: 0pt, justify: true)
set par(first-line-indent: 1.25cm, justify: true)
[The thesis is devoted to a mobile application for secure storage of user data (the Wallenc software product). Data is encrypted on the device before upload; decryption is performed only when the user enters a valid key. The work includes analysis of analogues, requirements, architecture and UI design, Kotlin implementation for Android, testing, and a brief economic assessment.]
[This explanatory note is devoted to the development of a mobile application for secure storage of user data (the Wallenc software product). It describes analysis of the subject area and analogues, requirements formulation, architecture and user interface design, software implementation in Kotlin (Android, Jetpack Compose, Room, Hilt), testing, and a brief economic assessment.]
parbreak()
[The application uses MVVM and Clean Architecture. Main features are local and remote vault management, client-side AES encryption, Room metadata storage, and Yandex OAuth integration.]
parbreak()
[Keywords: mobile application, client-side encryption, Android, vault, OAuth, Room.]
[Implemented: the VaultsManager → vault → storage → files hierarchy (one LocalVault on the device, remote vaults via OAuth), client-side AES encryption, service metadata in Room, and a project-level synchronization contour without passing encryption keys to the provider. The source code is hosted in a private GitLab repository at Southern Federal University. Full source listings are in Appendix A; software documentation is in Appendix B.]
}