mttcrsp / fosdem Goto Github PK

This would work nicely in the plan section. It can be used both as a fallback for when the user has not favorite event and has a tip in the top right of the plan screen.

Use links instead of licenses and remove all related files and dependencies.

This is only significant for the plan section as you are probably less interested in events that already took place.

Old versions of iOS, map views do not support camera boundaries. This means that users may end up inadvertently scrolling far from the FOSDEM area and have trouble going back to it.

To address this issue you could display a button that resets the camera to its initial position. This should be placed on the opposite site of the screen with respect to the compass view.

The current track screen implementation does not report the day(s) in which the track events will be held. Moreover it repeats the same room for all events.

Ideally this information should be displayed at the top of the screen near the name of the track.

Visual clues for room, track and speakers info should be translated into the appropriate accessibility information.

Support for new schedules should only be introduced when the initial version of the schedule is published.

At the same time the previous year should be archived in the Previous years section.

In the map section, the area of the map in which you can scroll around is bigger than its necessary. Reducing it this area makes the map easier to navigate.

The blueprints view is currently displayed the same exact way both in portrait and in landscape orientation. Ideally when in landscape it should end up being left aligned.

Carthage is still referenced in the Brewfile.

In order to make the more section more extensible, you need to modify how data for different informational screens displayed from it - history, developer rooms and so on - is stored.

Data for all of these screens should be defined within HTML files stored on disk that can be modified without updating the app.

These HTML files would the be rendered as attributed stings and displayed using TextViewController.

Bring back the old design. Make sure that header info is not announced separately from the event title by the Voiceover engine.

The Janson building overlay is missing a coordinate from its definition. This makes the the auditorium shape look particularly off.

Introduce an additional EventsViewControllerDataSource method so that clients can provide a custom header based on their context. In the track screen, the start start time of the event should be used as the header. In the search results screen, the track for the event should be used as the header. In the plan screen a more rich start/weekday/room combination should be used.

Replicate the Apple Developers app year UI by introducing icons for each year and extending the title with a slightly expanded conference name. (e.g. FOSDEM 2020)

There are two different ways to achieve this.

You can either introduce the date information as part of the Event model or do a lookup of the track associated with a given event and get the date from that.

The first one requires you to extend the XML parsing logic. The second one requires you to introduce a new service that stores all tracks in memory to allows you to lookup of the necessary information.

• Remove debug logs
• Rename attributesDict
• Extract element names properties

Glyphs for annotation views are not updated during transitions from and to dark mode.

The current implementation only reads the name of the track. That can be a bit jarring if you do not have any visual context.

When the app is launched check for the availability of updates by querying the AppStore search API for Fosdem apps, looking for this app and looking at the version field.

The current FT4 based search implementation is not really the best as it does not support things like partial matching, autocorrection and ranking of results.

It should say No events a starting in the next 30 minutes.

The appropriate location does not cover the nearby street. Redefine the coordinates for its overlay to fix the issue.

When displaying blueprints for a given building, the annotation for that same building should animate to the center of the visible portion of the map.

You should periodically poll the schedule API for updates. Keep in mind that this the payload returned by the schedule API is in the order of MBs so you do not want to frequently poll on cellular networks. Also consider providing a manual update button in the more settings together with a latest update indicator.