사용자에 마커 루트 정보를 저장하여 사용자 로컬 내에서 파일로 관리 할 수 있도록 하는 앱
- rnMapBoxApi
- rnBackgroundGeolocation
- sqlite
- reanimatedCarousel
- fileReducer
- 다크 라이트 모드 지원 => 완료
- 루트 위치 수정 기능 (현재 진행 중) => 완료
- 아이콘 커스텀화 => 완료
- 설정 화면에 사용자 커스텀 추가 => 완료
- 유저별 권한 관리를 통한 기능의 permission 제공
- 클라우드 위치 기록
- Oauth를 활용한 로그인 회원가입 지원 => 완료
- 마커, 루트, 파일 검색 기능 추가 위에 slider위에 검색 조건을 걸음 => 완료
- 이후 태그를 통해 #버섯 #산중턱 검색 할 수 있게 변경 => 진행 중 80%
-
- 경로 svg파일로 변환하기
- 파일 상세 보기 tab-view 제작 [마커 | 파일 리스트 | 루트] 이렇게 => 완료
- 스크롤 페이지네이션 lazy loading 추가 => 완료
npm create tamaguiThis monorepo is a starter for an Expo + Next.js + Tamagui + Solito app.
Many thanks to @FernandoTheRojo for the Solito starter monorepo which this was forked from. Check out his talk about using expo + next together at Next.js Conf 2021.
The main apps are:
-
expo(native) -
next(web) -
packagesshared packages across appsuiincludes your custom UI kit that will be optimized by Tamaguiappyou'll be importing most files fromapp/features(don't use ascreensfolder. organize by feature.)provider(all the providers that wrap the app, and some no-ops for Web.)
-
Install dependencies:
yarn -
Next.js local dev:
yarn web
To run with optimizer on in dev mode (just for testing, it's faster to leave it off): yarn web:extract. To build for production yarn web:prod.
To see debug output to verify the compiler, add // debug as a comment to the top of any file.
- Expo local dev:
yarn native
Note we're following the design systems guide and creating our own package for components.
See packages/ui named @my/ui for how this works.
If you're installing a JavaScript-only dependency that will be used across platforms, install it in packages/app:
cd packages/app
yarn add date-fns
cd ../..
yarnIf you're installing a library with any native code, you must install it in expo:
cd apps/expo
yarn add react-native-reanimated
cd ..
yarnyarn upgrade-interactiveYou can also install the native library inside of packages/app if you want to get autoimport for that package inside of the app folder. However, you need to be careful and install the exact same version in both packages. If the versions mismatch at all, you'll potentially get terrible bugs. This is a classic monorepo issue. I use lerna-update-wizard to help with this (you don't need to use Lerna to use that lib).
You may potentially want to have the native module transpiled for the next app. If you get error messages with Cannot use import statement outside a module, you may need to use transpilePackages in your next.config.js and add the module to the array there.
- Root:
apps/next - Install command to be
yarn set version stable && yarn install - Build command: leave default setting
- Output dir: leave default setting