Hello @rkresnadi, I’m happy to break these down here. May I ask that in the future to keep consistency in the architecture of the forum postings, would you consider creating separate posts for each different contextual item? This step allows for more accurate searches in the future and adds value to the Dropsource developer community as a whole. We all love your extremely valuable participation in the forum and would love to leverage that with posts that are searchable for other community members that have the same great questions you’re bringing up here.
Much the same as nesting scrolling elements within scrolling elements won’t create a good user experience, tappable elements with tappable elements nested within them will also not bode well for a clean experience for your users. Lists have cells and if those cells are tappable, adding a sub-element that is also tappable like a textfield is not advised. The app will not know what the user intends from the same tap. If you notice for instance in your phones Contacts app, in order to edit a contact, you can’t tap the cells contact name and edit it there. In that app you need to tap the cell to go into a details screen where there are editing workflows built on that screen. This is on purpose as the app wouldn’t know if you want to see contact details or adjust the name with that single tap on the cell.
This again feeds into the longer explanation in the above item. Nesting tappable items into other tappable items will not be a clean user experience. The recommendation is to adjust your design to introduce a cleaner workflow into your design. If you find yourself in a situation where the actual cell in the listview does not need to be tappable, you can turn this off in the styles pane for the listview. This will allow your textviews to be the only tappable element and the app will understand the reason for the user’s tap better.
Crashes on page with map and reverse geocode on web simulator
Unfortunately web simulators do not handle GPS abilities like the embedded hardware capabilities inside your actual phone does. When testing map/gps features, you’ll find a more reliable experience testing on your actual device in these situations. With the new pricing adjustments, all Dropsource Developers can test projects on devices now.
Android scroll view
We are aware and working on the issue when it comes to inferring intrinsic sizing for scrollviews. There is a issue currently being resolved on the Android side addressing this issue. Follow the forum to learn more on this development. Timeline has its completion before the end of the year but it’s also still in development so it’s good to know it’s on the way. Scrollviews are posing interesting challenges with the new Constraints engine and we appreciate all the feedback we’re receiving in our developer community member’s use cases associated with scrollviews in your apps. Thanks for your patience as we are working towards sorting out these gaps in our scrollview element implementation.