Write.as Development @writeas_dev@abunchtell.com

[#wfdev] AngeloStavrow opened writefreely-swiftui-multiplatform #52: Set lang and rtl properties on publish https://github.com/writeas/writefreely-swiftui-multiplatform/pull/52

#WriteFreely

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

#WriteFreely

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

#WriteFreely

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

#WriteFreely

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

#WriteFreely

[#wfdev] Closed writefreely-swiftui-multiplatform #42: Persist content locally https://github.com/writeas/writefreely-swiftui-multiplatform/pull/42

#WriteFreely

[#wfdev] Closed writefreely-swiftui-multiplatform #16: The PostStore/CollectionListModel must be persisted locally https://github.com/writeas/writefreely-swiftui-multiplatform/issues/16

#WriteFreely

[#wfdev] Closed writefreely-swiftui-multiplatform #47: Set collection for post https://github.com/writeas/writefreely-swiftui-multiplatform/pull/47

#WriteFreely

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

#WriteFreely

[#wfdev] thebaer opened writefreely-swiftui-multiplatform #49: Show instance name instead of "Collections" title https://github.com/writeas/writefreely-swiftui-multiplatform/issues/49

#WriteFreely

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

#WriteFreely

[#wfdev] New task - T763: Support storing images in S3 https://writefreely.org/tasks/763

[#wfdev] Closed T371: Show blog URL on Blogs page https://writefreely.org/tasks/371

[#wfdev] AngeloStavrow opened writefreely-swiftui-multiplatform #47: Set collection for post https://github.com/writeas/writefreely-swiftui-multiplatform/pull/47

#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.

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?

@snap_as was also the first product we launched separately from @write_as, and it was built on the assumption that an entirely separate codebase would be best.

The idea was that the applications would share common components (https://github.com/writeas/web-core), but would have separate application codebases and storage.

Deployment got harder as their platform shifted beneath us, and one day recently our entire site was replaced by a simple message that said, "We no longer support Go 1.9." That was a fun day!

https://discuss.write.as/t/snap-as-is-down/1694/3

A little background: this is driven by Google Cloud being a very, very bad cloud platform to build on as a small team.

We tried it in 2016 as an experiment, and a series of service deprecations since then have caused us downtime and meant us ultimately offering a stable, but stagnated service.