Meeting Outcomes

31/3

Meeting outcomes

• how should we maintain special namaz timings? (jummah/multiple jamath for jummah/eid/janaza)
  • there will be two types of masjid
    • 1. where masjid enters namaz timings preemptively
      • that way, we will have data of namaz for months down the line, which will be datetime (not just time as per current implementation)
    • 2. where masjid enters namaz regularly
      • this way, masjid will update data for next day regularly
      • issue with this is that, it is possible that masjid might forget to update data, in that case we will simply show the next namaz as per some defined sequence, and show unavailable time, as we dont have data to say if that namaz is over.
  • create issues:
    • create task for the rework, and plan in it
    • update the schema as per new design (maintain datetime for each individual jamaat instead of just time)
    • update function to return namaz for the current day, or specified day/month depend on what the frontend need
• studying Mauquit and what design we can take from it?
  • we liked how mauquit works and we will use the design mauquit has (at least the layout)
  • create issues for
    • decide which design elements we will use from mauquit
    • update the wireframe accordingly
    • rework implementation accordingly
• deadlines details (How to implement?)
  • milestone
  • monthly goals
  • fortnight goals
  • create issue for: divide tasks into fortnight/month target
• Admin panel issue
  • will design web optimized for mobile (not for desktop)

---

30/03

Meeting outcomes

• login flow is different from wireframe, do we use the flow in the wireframe or redesign it?
  • we will stick to wireframe
  • app will launch in guest mode
  • a token will be created for first launch which will be cached in storage and used for auth
  • user can login later on then, that token will be replaced by their login token
  • (will review again when audio streaming is implemented as it will require some change in the flow)
  • create issue to correct implementation
• Do we really want to change tab navigation when masjid screen is opened, doesn't seem like a good design (maybe move those icons on top bar instead)'
  • we will remove the extra buttons and keep just home and profile for now
  • instead of those navbar button we will use stack navigation as the depth is just 1 from home screen
  • create issue to remove other buttons from the wireframe
• looks weird when switches to home screen
  • should store is subbed flag in cache and use it to choose navigation correctly (instead of going from one screen to another which looks wierd)
  • create issue for: update wireframe to use diamond for is subed then choose screen accordingly
  • create issue for: correcting the implementation accordingly
• Admin page: what ui will masjid people use to update data about timing?
  • will create a webpage for it using htmx
  • create issues for it
• how should we maintain future namaz timings?
  • will keep data for the future as given by that masjid if that data is available (they can decide how long in future time they want to keep the data of)
  • if not, just show that data is not available... in that case the masjid will have to provide data regularly when namaz times are updated
  • we can even send notification to update the timings if they forget to do so
  • create issue for plan how to implement this
• will continue rest 31/3 10:30pm:
  • how should we maintain special namaz timings?
  • studying Mauquit and what design we can take from it?
  • deadlines details