Upgrade to Pro — share decks privately, control downloads, hide ads and more …

0->1 現場におけるReactNative

0->1 現場におけるReactNative

React Native | JMDC TECH Talk #1
- how should we start new project
- how should we implement (especially RN project)
- how should we negotiate schedule with business side persons

In order to create a good architecture, sometimes we need to discuss due date vs internal quality.
For these cases, we can reduce cost and have enough time to consider "What is the best ???" by using strategy I showed in this slide.

I'm not sure whether my experience would be a help, but... if you want, I'd happy to translate it.

@YutamaKotaro

January 27, 2022
Tweet

More Decks by @YutamaKotaro

Other Decks in Programming

Transcript

  1. モバイルとアプリのデザインを見てみると、 
 0,1段階では類似していることもしばしば・・・ Form Form Web side App side -

    ほぼ同じ - 将来的にAppUXが作られる 共通化しても 
   無駄が多い・・・?? ,1T*UVWX:Y
  2. それぞれで作ると・・・・ Form Form Web side App side ,1T*UVWX:Y 頑張っても1.6(1 +

    0.6) 
 くらいのコストがかかる。 変更があると少し大変・・・🥲
  3. Form Form Web side App side ,1T*UVWX:Y 1.1(1 + 0.1)

    
 くらいでDay0完了 変更も楽々対応😀 局所ガワネイティブを使った場合は
  4. - Neglecting internal quality leads to rapid build up of

    cruft - This cruft slows down feature development - Even a great team produces cruft, but by keeping internal quality high, is able to keep it under control. - High internal quality keeps cruft to a minimum, allowing a team to add features with less effort, time, and cost From martinfowler.com "K%LMGHNNOSZ[\
  5. ビジネスサイドとの折り合いがつかない時もありま すが・・・・ A common debate in software development projects is

    between spending time on improving the quality of the software versus concentrating on releasing more valuable features. The "cost" of high internal quality software is negative. The usual trade-off between cost and quality, one that we are used to for most decisions in our life, does not make sense with the internal quality of software. From martinfowler.com "K%LMGHNNOSZ[\