Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rewrite #163

Open
kiliankoe opened this issue May 21, 2017 · 0 comments
Open

Rewrite #163

kiliankoe opened this issue May 21, 2017 · 0 comments

Comments

@kiliankoe
Copy link
Owner

kiliankoe commented May 21, 2017

I haven't really put a lot of time into this app lately and when I did get around to it, there's just too much to run into, rip out and start over with. Most of that is due to the fact that this was my first iOS project and started out in Swift 1.0 (!). The overall design (code-wise and the UI) really isn't that well thought-out and can be massively improved. I'm getting a strong feeling that the sane thing to do at this point is to just scrap the old project and start over with the lessons learned. Rethink what kind of data the app shows and streamline that.

Some random thoughts on this topic that have been floating around in my head, not an exhaustive list:

  • Map view (or split map/table) should be the default
    • What about a drawer like design like the new Maps.app? Does that make sense here?
  • Map annotations should display more information, see Windows version of ParkenDD
    • In fact, the Windows UI has always been pretty damn awesome! Cheers, @sibbl 🎉
  • It should be much more obvious that more cities besides Dresden exist
    • I'm still all for renaming the application, but all ideas like "Parking", "Parken", "OpenPark" stink 😕
  • Navigation to lots should be possible, but it would probably make sense to leave this to other apps (see Karte)
  • Keep the codebase clean and use ParkKit
  • Throw a Patreon-esque IAP option somewhere, see "old" Overcast or ChatSecure
    • No essential features (if any) should be behind the IAP though
  • Evaluate the use of a local trained neural net for forecast info (🏓 @absolute-heike about this)
  • Possibly send out push notifications for new cities (would obviously require this to be added to the backend as well)
  • Try and make a lot more use of testing and automation tools like fastlane to make publishing updates on this project not so much of a chore^^
  • I planned to use more system extensions points quite a way back now, but never got around to that. This app could work pretty well with a Today extension and Watch companion app.
  • Evaluate the use of MapBox instead of Apple's MapKit
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant