Confirmed users
1,225
edits
| Line 95: | Line 95: | ||
** Francisco has also to check with Wilson, as when he created the pods, he created them without enabling them to use swift or dynamic frameworks (It seems it's a flag). The problem is that when executing pods install, it's getting crazy. | ** Francisco has also to check with Wilson, as when he created the pods, he created them without enabling them to use swift or dynamic frameworks (It seems it's a flag). The problem is that when executing pods install, it's getting crazy. | ||
** So far Francisco has committed it and merged, if you debug you can see the compass component pointing to the Shark and you can see how it moves and the direction changes. It's written in native, not java script. It's working fine, there could be issues if you are in the antipodes. Wilson says that if we are very far from the point we could hide the compass to avoid issues, we can play around | ** So far Francisco has committed it and merged, if you debug you can see the compass component pointing to the Shark and you can see how it moves and the direction changes. It's written in native, not java script. It's working fine, there could be issues if you are in the antipodes. Wilson says that if we are very far from the point we could hide the compass to avoid issues, we can play around | ||
* Waffle connected to, what repos?: Journey, Journey services. We would need to disconnect the rest of repos. | * Waffle connected to, what repos?: Journey, Journey services. We would need to disconnect the rest of repos. | ||
** Scanners ones? We will use it after releasing the first version of the app. In the previous version we had the GPS and the physical web scanners together, we would need to create one repo specific for the Geolocation staff in Journey | ** Scanners ones? We will use it after releasing the first version of the app. In the previous version we had the GPS and the physical web scanners together, we would need to create one repo specific for the Geolocation staff in Journey | ||
* What happens if we need to use "Project Magnet" name for the beta version of the app we are working on? It would be really bad if we had to use the same name because users will update the app and we'll download a complete different application without physical browser. Right now the documentation in github is really confusing. Journey is a code name and we are waiting for Porfirio to let us know about the definitive name | * What happens if we need to use "Project Magnet" name for the beta version of the app we are working on? It would be really bad if we had to use the same name because users will update the app and we'll download a complete different application without physical browser. Right now the documentation in github is really confusing. Journey is a code name and we are waiting for Porfirio to let us know about the definitive name | ||
* Visual Work: agreed with the Agency the probable timeline (Start Date: Jan 30th, Deadline: March 3rd) | * Visual Work: agreed with the Agency the probable timeline (Start Date: Jan 30th, Deadline: March 3rd) | ||
* Usability Test? Possible dates 20th Feb - 24th Feb while Jakuv (Visual designer) is on PTO that week. We could do the final refinements the following week. | * Usability Test? Possible dates 20th Feb - 24th Feb while Jakuv (Visual designer) is on PTO that week. We could do the final refinements the following week. | ||
** Francis thinks that we could start the recruitment the following week to have time in advance. He thinks Vancouver could be the place, as Mihaela is there and also Wilson. Other interesting option could be split the participants in London and in Vancouver but it's better | ** Francis thinks that we could start the recruitment the following week to have time in advance. He thinks Vancouver could be the place, as Mihaela is there and also Wilson. Other interesting option could be split the participants in London and in Vancouver but it's better | ||