Skip to content

Passcodes Project

An app that takes down your headache of remembering passwords and authentication related sensitive information in your head.. It is a secure and robust solution that not only, let you store passwords in a local storage. but also make the experience, much more fun and initiative..

Outline

Problem Statement

In modern days, data is important. especially data that has concern with authentication information... and store that securely is a serious task (and much of headache). passcodes try to eliminate this headache. by provide you with a simple, sweet and initiative ui that help you store your passwords in your local storage. (and to an extend also in cloud). which means, you have full control of data that you share with passcodes app.

Goals

  • To make password management process much more intuitive, enjoyable & customizable. By give you full (or utter most) control over your authentication infomation stored in our app.
  • To simplify password management, yet give extensive control to end users.
  • To serve as a guide, reference & extensible tool, for all people (nerds) who are interested in making thier password management workflow, much more safe, secure and customizable.

Target Users

  1. Not So Developer, Not So Normal-End-User First:

    Which means, - For those, who wish to optimize, there password management workflow.. but don't know how to... - For those, who are willing to spend time learning a tool (especially for password management) and for those how are willing to uncover (disambiguate) abstraction that app uses to make the experience of storing passwords much more easier... - For those, who are willing to gain control of there auth data, without that extra headache of remember data that comes with it... - For those, who don't mind researching and squirm through our documentation for hrs, just for once in a while, to customize & optimize their password management workflow...

  2. Software Engineer is our second target users:

    Which means, - the source code of the app, will be clean, maintainable and extensible for future extensivity... - developers can adpot the app to thier need... we will also have documentation that one could follow & learn from, about how to extend passcodes app...

  3. End Users are the least target's of application:

    Which means, - we will try to abstract away the complex concepts in different extensible/decoupled systems... so, end users will be more likely feel at ease while using passcodes app... - if you fall in this category of target users, then it more likely that you will either move off the app early on. or would like adopt and become password management nerd yourselvous; as the app is fully optimized to lead you towards customizing and optimizing of your password management workflow... - Also, it more likely a way to start using/integrating passcodes into your daily password management workflow... but if wanna continue, then we recommend you, to try learning about your specific password management workflow and make yourselvous prompted from just a end user to a more better target group.

Priorities

Customization & Extensibility is our top most priority, While simplicity is just not!!:

App will be fully (or to it most) be extensible & customizable, without limited by any abstraction and simplification of app. We as developer will try to make the internals of app more abstract and decoupled and thus, customizable. meanwhile, we might loss simplicity... and the UI/UX might look more complex then need...

Simplicity is not priority of the passcodes. but abstracting concepts from users (as much as possible) surely is...

Security is our second most priority, While performance is just not!!

Which clearly says that app might have a ten different redundant, in software checks for data and user input. to ensure a robust operation.. This check might add performance overhead.. but we will ignore this, as we focus more on security, robustness and extensibility.

Also, performance is not even a thing, we consider optimizing for, while making passcodes app. and it's done for better or for worse. as passcodes app is not use daily. and also we believe, that security concerns associated wih password management app is more important then any performance issue ever arise could, and sure in modern world we have high speed computer and three different redundant check won;t hurt. but an app crash or data corruption might, As the data app deals with is highly sensitive, considering end user might end up save all there account form all different platform at one place....

But that surely, this doesn't mean we will not focus on performance... if it became a serious issue we will try our best to solve the performance issues... but it just that, we might end up wait until something goes seriously go wrong with performance!! (e.g. app take time, to process a simple single store password action.. for straight 1 minute...)

Motivations

We have pretty good and decent motivation that drive us forwards, thier are two previous project that back passcodes app... that were made previously by me(jeeldobariya38) and fellow contributor's...

Kupass

Github: Kupass.

Overview

It's a simple & much more intuitive password management solution.. develop by fellow contributor, daniel (@kudanilll). It is one of recommended solution if you want to have easy to use app.. and don't need complexity and customization that passcodes offer you. as it simple and intuitive.. it is very much more secure as it all in your local storage...

Why Quit?

Daniel, the official owner of project, has stop provide further update as his priority changed... there was no real issue with the project... it just that project was more made for educational purpose and prototyping, hobby kind of purpose.

Smart Manager

Github: Smart Manager

Overview

It was my first project in world of password manager and also in world of software engineering... a project where I have made a lots of design mistakes... while trying to make the codebase more scalable and extensible and tried implementing various stuff, that just don't fit together.. its a perfect example, of using everything someone say is a community standard, without ever questioning why am i using it or whether is it worth adding to our project.... it like if someone said using dependency injection make code better... then let just use it in our project....

Why Quit?

The project suffer from major design issue that, I realized very later, in project timeline. it happens to reach to the point where the code was literally just mess and it just don;t have core features... so i thing to dump the app, and idea as whole... never really thought that I might come back to same idea a year after and use it to build a app in android and beyond...