Show newer

@ahangarha Are there any improvements you'd suggest? We're completely open to any of your feedback on that pull request!

[] AngeloStavrow opened writefreely-swiftui-multiplatform #51: Add support link to settings screen in iOS target github.com/writeas/writefreely

[] AngeloStavrow opened writefreely-swiftui-multiplatform #50: Set new local post as selectedPost in WriteFreelyModel github.com/writeas/writefreely

[] Closed writefreely-swiftui-multiplatform #17: Set the a Collection for a Post based on selectedCollection w/ Drafts fallback github.com/writeas/writefreely

[] Closed writefreely-swiftui-multiplatform #23: [iOS] Close button does not dismiss Settings sheet after logging in github.com/writeas/writefreely

[] Closed writefreely-swiftui-multiplatform #48: Move sheet modifier for SettingsView outside of NavigationView github.com/writeas/writefreely

[] AngeloStavrow opened writefreely-swiftui-multiplatform #48: Move sheet modifier for SettingsView outside of NavigationView github.com/writeas/writefreely

So, starting with @submit_as, we built the functionality into the Write.as codebase. There was still plenty of copy-paste involved, but we were able to launch this new product much more quickly.

Now instead of creating separate apps first, we're building them into Write.as first and then separating out functionality over time.

Show thread

This might've been a good theory for building modular applications (as I'm hoping to), but in practice causes a ton of headaches for maintenance and end user experience.

Little problems came up right away:

- How do we share user data across platforms?
- How do we create common UI patterns while keeping distinct branding on each platform?
- How do we reconcile slightly-different uses of those shared libraries across platforms?

Show thread
Show older

Write.as Development's choices:

A Bunch Tell

This instance is only for A Bunch Tell projects.