JohnPollard-hybrid-app-RailsConf2024.pptx

Editor's Notes

1. In other words, Key word stuffing in your presentation title. 
2. In other words, Key word stuffing in your presentation title. 
3. This influence the rest of your decisions. 
4. Should this be before 90% parity? 
5. Do a lot with a little. We want to move quickly. I want to build fun things with fun people. More people multiplies the complexity to the team. 
6. should move to later?
7. Do a lot with a little. We want to move quickly. I want to build fun things with fun people. More people multiplies the complexity to the team. 
8. Important to understand that the navigation in the app is decided before the page is requested. You can’t use the response (like redirects) to decide how to present the next screen.Navigation between pages is decided on request. While native interactions on a single page with Strada is after the response.That has been a pain point with the rails teams I’ve worked with. You are used to being able to defer navigation decisions.HTTP in the rails way is stateless. You don’t care where you came from. You can just send them where ever you want.Native UI (more so on iOS) is very stateful. You can’t go to the next place without understanding where you are and sequencing the navigation transitions.
9. put on the slide each navigation bar item is a tab 
10. you will always have a path configuration file with turbo native
11. The "path configuration" is a feature that simplifies mapping various urls to "path properties". When possible, it's preferred to get data for a page from the page itself through the DOM or a library like Strada (see advanced). However, certain properties you need to know before the page loads. This can be anything you want from the title, the background color, the presentation, or which view controller to load. Using a path configuration is completely optional and not required to use Turbo iOS.Important to understand that the navigation in the app is decided before the page is requested. You can’t use the response (like redirects) to decide how to present the next screen.Navigation between pages is decided on request. While native interactions on a single page with Strada is after the response.That has been a pain point with the rails teams I’ve worked with. You are used to being able to defer navigation decisions.HTTP in the rails way is stateless. You don’t care where you came from. You can just send them where ever you want.Native UI (more so on iOS) is very stateful. You can’t go to the next place without understanding where you are and sequencing the navigation transitions.
12. what tab gets loaded first?
13. controller is driving the web and mobile apps
14. what other things can you do?add a link to documentaiton
15. what about androind in terms of icons
16. what about androind in terms of icons
17. The specific value of the quota is an implementation detail, and it can be changed by Google Play without any notice.
18. When I go through these values, I think there's one area that sticks out: - We take the time to find the best solution.