-
Live tweeting the Tuesday edition of #TouchlabShare "Identifying app components for high impact code sharing" @TouchlabHQ/1246093631292706816Permalink
♻️ 2 Retweets ❤️ 5 Favorites Mood 0
-
Get a list of advocates from your iOS and Android team to understand what's important, what are the painpoints, how code is structured on both sides, and figuring out where both teams will get the most benefit #TouchlabSharePermalink
-
If everyone hates CoreData, start there 😜 Otherwise, look for areas with a significant amount of business logic #TouchlabSharePermalink
-
Examples: * Managing critical state in an onboarding process * Handling caching for offline mode #TouchlabSharePermalink
-
Areas that strictly require alignment between the two platforms are great places to start. E.g. * Handling network responses * Analytics events #TouchlabSharePermalink
-
If there's a piece of code that was written 5 years ago and no one has had to touch it -- "if it works, don't fix it" -- don't put that high on your list to code share. Instead, look at which parts of the code are active or will be active based on your roadmap. #TouchlabShare
-
You are probably already modularizing, separating concerns, keeping your code clean. We find that starting out with code that's already cleanly separated is a great place to start trying out shared coding A lot of well-architected code is already sharable. #TouchlabSharePermalink
-
In Q&A now. We'll be tweeting out Q&A in the future from the @TouchlabHQ account. If you want to be part of it now. Register and join #TouchlabShare on Zoom: zoom.us/meeting/register/tZcrcu6qqDwvpfYfRWO8YrZExVRRQOMXHQPermalink