BlinklessBloom

BlinklessBloom is a habit-tracking web application built to help people build a life of consistency through simple daily routines, encouraging design rather than pressure or guilt. The vision behind the app is growth. Growth doesn�t come from big dramatic changes but from the small, repeated actions taken every single day, even when nobody is watching.
The app is organized into four main sections. The Feed section shows a community timeline where users can see habits completely by others, with likes and leave comments.The goal for this is accountability and encouragement similar to the way social validation can make consistency feel less isolating. The Habits section is where users add and manage their personal habits, sorted into categories like Health, Mind, Creative and Growth and check them off as they complete them each day. The Progress section visualizes monthly consistency through a sunflower that gains petals as more days are completed, a small, satisfying visual reward tied directly to real effort. Finally, the Profiles section introduces a light game based interface layer were users start as a bunny and can progress through Sheep, Knagaroo and finally a lion by completing full months of consistent habit tracking, giving long-term motivation beyond just daily check marks.
This web application is built in two phases, the front-end and back-end . The front-end which is the actual interface a user sees and interacts with which was built using HTML for structure, CSS for styling and animation, and JavaScript to handle all the interactive logic such as adding and completing habits, calculating monthly progress percentages,generating the sunflower petal count, handling the sign-in/login flow and rendering the community feed dynamically. At this stage all data was stored using the browser�s local-storage. This worked for testing and demonstrating functionality. But now in phase 2 which is the back-end where the project will become a full -stack application, building a back-end suing PHP and MySQL. This phase will require relational database design rather than just JavaScript objects. I�m designing seven interconnected tables for my database, which are, users, habits, habits logs, progress_log, feed_posts, post_likes and post_comments, each linked together using primary keys and foreign keys. Tables such as post_likes and post_ comments are all bridge tables, existing specifically to resolve many-to-many relationships, since one user can like many posts and one post can be likes by many different users.

Having the database structure complete, the next stage will involve writing a series of PHP scripts that acts as the communication layer between the website and database. Each script will be responsible for specific tasks such as the register.php and login.php will handle account creation and authentication by inserting into and querying the user table. Add_habit.php and get_habit.php will manage creating and retrieving a user�s personal habit list. Toggle_habit.php will update completion status and log it into habit_logs, then get_progress.php will calculate and return the daily and monthly statistics that power the sunflower visualization. The community feed will require slightly more complex scripts such as get_feed.php which will need to join data across feed_posts, post_likes and post_comments simultaneously to reconstruct a complete, readable feed for the front-end to display.
Once that is done, there will be rewriting of JavaScript file, so instead of reading from the local storage, they will send and receive data using fetch() request to these PHP endpoints. BlinklessBloom is intended to represent more than just a habit tracker but also demonstrate the transitioning from front-end to back-end layer. It will function the way a real, production level application would with user accounts and secure authentication, real community and data will no longer disappear the moment the browser�s cache is cleared.