After several years of migration to multiplatform, it is finally done!
Time to party! But also, to test! I expect many small and big things to be found during the beta. The earlier they are found, the shinier the public release will be .
The above version (v64.0.0) released on September 30th is equal to the Android release v64.0-alpha2, see the changelog for the alpha1 and alpha2.
If you are not sure whether something is a bug, best discuss it first before filing an issue.
Known caveats
you can only use the back gesture rather than clicking anywhere on the map to cancel a form. Likewise, it is currently not possible to directly open another quest/overlay element while a form is open.
Map fails to render oniOS 15.x
well, any bug already reported. So, before reporting bugs, check what’s there already!
If I were you, I would not prioritize scarce resources on iOS 15 support for a new app. On CoMaps that is less than 1% of the user base, and there were none active on TestFlights so we shipped a broken UI update recently :)
For a new app I would actually target iOS 18 as all phones that can run iOS 17 can run iOS 18.
Closing the form as you say is not very intuitive, and I’m actually not able to perform it now (it did work a couple times for me!), so stuck with an open quest.
Clicking on the map to dismiss it is one thing, but the quest form also shows the drag handler, so you could also allow swiping the drag handler down to close? Or remove the non-functioning drag handler?
Well, the drag handle is always shown, even if the form cannot be expanded (because it is not that large). The drag handler is for making the form larger, like the bottom sheet in which I am writing the reply in right now. Just like with the sheet here, the drag handler cannot be used to close the form. I think it would be unintuitive, as swiping down a bottom sheet is rather associated with minimizing rather than closing. The expectation would be that it’s still there, just not visible, or just peeking out a bit.
I suppose the drag handle could be hidden if the form is not actually large enough that it needs to be extended.
What is definitely planned is to close the form on map click (after asking whether to discard any changes, if any were made). One thing I am unsure of right now, whether there should be a ← (back) button additionally, displayed e.g. left of the quest title.
Best of luck, this is a huge move for iOS users. I would love to help, but sadly my iPhone (SE, 2016…) has reached its end of life for updates, so can’t run testflight
Huge thank you for all the work y’all’ve put in to get this far! I actually bought an android to use streetcomplete so I’m tremendously excited to have it on my main phone.
Aw! As a proponent of open source, I should be sad but as Android is becoming a closed platform too, ¯\_(ツ)_/¯
By the way, the road is now open to create a Linux phone version (Jolla, Nura, PureOS, Ubuntu Touch, …) with very manageable effort. Although, of course, probably the app worked on these all along more or less as I’d expect that they all offer an Android compatibility layer (Waydroid).
Same here, so I love that you will support Ios 15! But how would the testing would work, since Testflight isn’t available? Do we just wait for public release on the App Store @westnordost?
Well, a shame that TestFlight isn’t available on iOS 15. I guess an early sign for support for iOS 15 being dropped in developer tools soon, too.
I have an iPhone SE (2016) myself and occasionally test on it. No guarantee that I’ll find everything that would only not work with iOS 15.5, but it’s something. I think the app will be reasonably bug-free once it hits the app store.
Since this was posted on Hacker News yesterday, there are now about 2000 (of max 10000) TestFlight testers!
Also, just now I found out that testers can leave feedback, with screenshots, (and crash reports) which are displayed one a page app store connect. And there is a lot of it. I am away this weekend, but I will look through it starting Monday. The next TestFlight alpha is already in the pipeline and will be available in a short while.
Changes here:
(Most importantly, fixes two common crashes and the fact that one couldn’t exit forms by clicking on the map but only via the back gesture, which not well known at all for iOS users)
By the way, I love the small size of the iPhone SE (2016), which would incidentally also be the smallest screen on which StreetComplete would run. (Which might be the source of a few displaying issues.)
For upgrading to the next more modern iPhone, I guess the iPhone Mini 12 or 13 would be the next best choice. They are actually smaller than the iPhone SE 2020 and 2022, just the screen is bigger.
well, old versions are always about to be dropped, ios 15 is from 2021, but the cut just happened a month or so ago, where ios15 was set as a minimum requirement, before you could publish apps with ios12.
Perhaps a stupid question, but are our submissions using the TestFlight app actually being used? As in, are they updating the live OSM maps? I’ve done loads of quests already and I hope I won’t have to redo them when the app is out of beta.
As an iOS user, I’m so glad to finally get this app – thank you! It is very well designed.
.
But how would the testing would work, since Testflight isn’t available? 
Do we just wait for public release on the App Store 
I am away this weekend, but I will look through it starting Monday. The next TestFlight alpha is already in the pipeline and will be available in a short while.