Skip Navigation

[Update] v1.0.4b (iOS focused) update in review, short summary

I am prepping a larger overview to cover all the changes made in v1.0.3b, but it is kinda late and still would like to share a quick update.

I feel very satisfied with how all of the underlying packages supporting Loom have gained lots of needed robustness all around. I view this to be close to the real beta. Probably should have called v1-1.0.3b Alpha.

This week, expect lots of refinements that will be much more consumer facing/front-end.

Details:

iPad and macOS versions will be ready by v1.0.4b (2). Still some things need to be revised.

Community info view (which triggers subscribe) will be functional again in v1.0.4b(2). It is inactive for this version.

  • Share screen shots of comments and posts, auto-generated
  • Slideable menu on the main feed
  • Keyboard toolbar for quick markdown shortcuts and other quality of life needs. A great little feature to keep adding to in the future.
  • Improve speed of modals appearing and navigation overall
    • Granite has been updated with a custom navigation stack. I am working on documentation to help share how to utilize this for your own applications. When working with multiple form factors and or client types (iPad/iPhone/mac) I found this solution I incorporated to be simple and powerful.
  • Names of Looms are editable again
  • Content actions revised and hooked (there's many ways to do things, so I am still making sure I get them all)
    • Edit
    • Viewing Post content
    • Block (Feed)
    • Share
    • (There are others being worked on or checked for completion, like Report)
  • Fixed image uploading, compression occurs prior. This will be customizable in a future update. It is currently targeting 100kb.
  • Lots of nitpick adjustments to design overall

Major Known Issues:

  • Login and Add Account modals dismiss prematurely. Essentially one won’t be able to login.
  • Endless spiral for loading collections of any kind, feed, community listing, post content. Simply refresh to fix it. The issue is known, just haven’t resolved yet.

Lot's more to cover. Wanted to get this build out and start the v1.0.4b journey, as I felt the quality has increased by quite a bit since the initial v1.0.3b.

0
0 comments