Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mobile Development #2

Open
wants to merge 9 commits into
base: main
Choose a base branch
from
Open

Mobile Development #2

wants to merge 9 commits into from

Conversation

PureZinc
Copy link
Collaborator

@PureZinc PureZinc commented Dec 2, 2023

We're finally ready to build the mobile app with React Native!

New Features:
    - Added Journaling:
        - User writes in JournalPages,
        - In the Database, ach page belongs to a journal of different types.
        - Database designed that way because some journals may have more than one page

    - 2 New Journals (Empty Page, Random Prompt)!
    - View the journals you've previously written in the My Journals component (unfinished).

Journaling Features in the Future:
    -> Making the Submit button in the JournalingPage Component create both the Journal and the JournalPages!
        - Right now, clicking on the JournalingChoices components create the journal, which is pretty ugly.
    -> Better development of the Journal Types system
        - If anyone wanted to add an extra Journal Type, they'd have to
        go into backend/journaling/models and add an extra Journal Type, then they'd have to
        go into the frontend and do a ton of other things all at once.
        - This makes life harder, and it will get fixed in the near future.
    -> Making the View Content button actually view the Content
        - The MyJournals page is currently unfinished.

Bigger Features:
    -> Authentication system
    -> Habit Tracker
    -> AI Bot
Added:
    -> Journaling FEATURE
        - Database: The journalng app's database structure has the main journal
        of a specific type (Empty Page or Random Prompt). The user writes in a
        JournalPage, which contains a Prompt and an Entry. The database is
        structured this way because some journals may contain many journaling
        pages.
        - Frontend: Users can choose from either an Empty Page or a Random Prompt
        journal. Empty Pages allow the users to write their own Prompt, while the
        Random Prompt generates a random prompt for the user.

Future Updates:
    -> Making the Journaling app better
        - Right now, it's difficult and tedious for a dev to make a new Journal Type.
        They have to go into backend/journaling/models and add the type in Journal.TYPES,
        and then create a new JournalingPage component in frontend and then develop the rules
        for it. There will be an easier way of journal_type creation in the future.
        - Clicking on a JournalingChoices button will create a Journal object before the
        User edits a JournalPage. The Journal and JournalingPages should be created
        at the same time.
        - The MyJournals page is unfinished.
    -> Extra Features
        - Authentication app
        - Habit Tracker app
        - An AI Bot that can guide your
        - Other self-improvement/productivity stuff
This is the last commit before we start moving to React Native
This branch is where we develop for the Mobile Server
Changes to be committed:
new file:   frontendMobile/src/Api/apiEndpoints.js
    - This file contains all the endpoints the frontend will interact with
    - This makes life easier, since you don't have to rewrite the same endpoints constantly
    - It also helps frontend devs and backend devs communicate a lot better
new file:   frontendMobile/src/Styles/Styles.js
    - This file controls the UI/UX design of the App
    - This file will be used the most by UI/UX designers
    - In the future, users will be able to choose their own design (That's why the styles are in seperate folders.)
This is the README for the mobile-dev branch.
Copy link

vercel bot commented Dec 2, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
stoistrom-react-django ❌ Failed (Inspect) Dec 4, 2023 10:17pm

Copy link
Member

@dinxsh dinxsh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

kindly paste the vercel deployment error here to check where it went wrong

things you can work on

  • rename folders to and files to camelCase and maintain it throughout the codebase
  • test code before pushing and ensure it works properly on your device
  • check https://cbea.ms/git-commit/ and make commit or pr messages more descriptive

@PureZinc
Copy link
Collaborator Author

PureZinc commented Dec 5, 2023

Team Access Required

You are signed in as purezinc.

You cannot access this
unique deployment URL
as you are not a member of the team. You can view the latest version of this branch by requesting access to the
up-to-date deployment URL
.

This is the error I got when I tried deploying my changes with Vercel. It seems that I can't deploy my changes because I'm not in the vercel team group.

@dinxsh dinxsh self-assigned this Dec 5, 2023
@dinxsh dinxsh added the enhancement New feature or request label Dec 5, 2023
@dinxsh
Copy link
Member

dinxsh commented Dec 8, 2023

Team Access Required

You are signed in as purezinc.

You cannot access this unique deployment URL as you are not a member of the team. You can view the latest version of this branch by requesting access to the up-to-date deployment URL .

This is the error I got when I tried deploying my changes with Vercel. It seems that I can't deploy my changes because I'm not in the vercel team group.

no worries, I'll deploy the backend on my vercel account for now and fix any issues related to the development being broken, will update any changes needed to this branch and let you know @PureZinc

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants