This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-05-03
Channels
- # admin-announcements (6)
- # beginners (73)
- # boot (84)
- # cider (9)
- # cljs-edn (5)
- # cljs-site (8)
- # cljsrn (2)
- # clojure (158)
- # clojure-austin (1)
- # clojure-canada (1)
- # clojure-dusseldorf (2)
- # clojure-ireland (1)
- # clojure-russia (45)
- # clojure-sg (2)
- # clojure-uk (28)
- # clojurebridge (2)
- # clojurescript (142)
- # core-async (43)
- # cursive (23)
- # datascript (5)
- # datomic (9)
- # dirac (4)
- # emacs (23)
- # funcool (1)
- # garden (1)
- # hoplon (280)
- # jobs (1)
- # ldnclj (6)
- # leiningen (37)
- # luminus (6)
- # om (30)
- # om-next (1)
- # onyx (6)
- # perun (24)
- # re-frame (10)
- # reagent (20)
- # remote-jobs (1)
- # rethinkdb (2)
- # ring-swagger (4)
- # rum (3)
- # spacemacs (6)
- # untangled (36)
- # yada (5)
@vikeri: Thank you for the links – It would be still great to have more information on the Android respectively iOS specific patterns – but that's probably a starting point for future contribution 😉 – I found this here very helpful to get started: https://github.com/alwx/luno-react-native
@anatoly: Yes, I’ve been thinking a lot about that lately. Luno is a great example of going ”native” on both platforms. But many apps have a similar look on both Android and iOS and thus even more code can be shared. I’m considering this myself in the project I’m developing and initially I wanted native look (Material Design/iOS specific stuff) but I think I’ll go with a more unified style for both operating systems now. Developed a basic Tab-bar to be used in both Android and iOS for example.