dpora Updates

dpora.com

Open call for collaborators!

We now have a working Android prototype, although admittedly a bit janky. As a single developer, I would love some help! If you’re familiar with the Flutter framework and share a similar vision for dpora, please send me a message at

Privacy policy

There is not much of a privacy policy at dpora because not much of your information is saved. Every time you submit a comment, it overwrites your last comment. There is no history of comments saved. dpora also does not collect personal

Version 1.4

There are some improvements and new features debuting with version 1.4. You can now change groups whenever desired. So, if changing the topic doesn’t help stimulate the conversation, perhaps a group change is in order. Also, when all

App is live on Google Play!

The dpora app(version 1.2) is now publicly available in 24 countries on Google Play. Google Play and the Google Play logo are trademarks of Google LLC.

App submitted to Google and Amazon

The first Android production version of the dpora app is done and has been submitted to the Google Play Store yesterday and to the Amazon Appstore today. There were a few added features, bug fixes and design changes during the testing

Terms of service

You must be at least 18 years old to use this app (dpora). dpora is not responsible for, and does not save a history of, user-created chat content. dpora is also not liable for any consequences attributed to the use of this app.

New UI additions

The user interface (UI) has been improved. Simple instructions (or a topic category) now show up alongside the discussion topics, with a related small icon. Over time, the icon will be enough of a hint without having to read the simple

Brick by brick

Progress has been chugging along while creating all the essential elements. A big checklist item completed is the menu link, which now shows a functional sliding drawer with contents. Smaller completed items include disappearing text,

Major progress on responsive design

Dark mode will be the default (and the only option) on launch. Also, the first release will be a progressive web app, followed shortly by an Android app. Therefore, from the beginning, the design needs to be responsive to both landscape