Need some assessment on several features.
Posted: Thu Jul 16, 2020 11:15 am
Hi there,
I am new to LC and have worked my self through a few tutorials, examples, etc. and feel confident to build my mobile app I have finished wireframing. Since there are a few things I will need to implement, I would like to have some feedback on them from you as expert before I start.
I can’t really estimate, if there are any showstoppers, if there are pitfalls etc. I need to be aware of. I googled a few things and found some old material, YouTube videos and discussions (e. g. in this forum) concerning a few things I have in mind.
Therefore it would be great if you could give me some insights/comments/thoughts on the following features I will need to implement, concerning
- „Dooability“. Can I build this feature at all? Is the framework up to date? What are mentionable limitations?
- How would you estimate the workload from your perspective? (hours, days, weeks)
- What should I focus on when starting to implement the feature?
Thanks a million and greetings from Cologne :-)
Maps
- Show cluster of items on a map. Zoom in to see smaller clusters and exact position of items.
- Set radius on a map (wherein something should be found e. g.)
- Set point on map as reference (fixed needle, pan/zooming map)
- Search for a location on map (postal code, street name, POI, etc.)
- use google maps on android and Apple Maps on iOS
In-app purchasing
- Buy a combination of four items (16 combinations)
Notification
- Push notification for three different triggers
Location tracking
- Constantly check where the user is (after agreeing to do so of course)
- Check location against GPS coordinates in server database table
Chat
- Very simple chat for two users to communicate (text only)
Language support
- Change language depending of the language set on the device
- Change language manually
Server communication
- Get items which include an image, plain text and GPS coordinates
- Search through that table on demand and when using location tracking
- Pre-caching of data to minimize server requests (costs)
Android and iOS support
- For everything listed above
- Notch support for both devices e. g.
I am new to LC and have worked my self through a few tutorials, examples, etc. and feel confident to build my mobile app I have finished wireframing. Since there are a few things I will need to implement, I would like to have some feedback on them from you as expert before I start.
I can’t really estimate, if there are any showstoppers, if there are pitfalls etc. I need to be aware of. I googled a few things and found some old material, YouTube videos and discussions (e. g. in this forum) concerning a few things I have in mind.
Therefore it would be great if you could give me some insights/comments/thoughts on the following features I will need to implement, concerning
- „Dooability“. Can I build this feature at all? Is the framework up to date? What are mentionable limitations?
- How would you estimate the workload from your perspective? (hours, days, weeks)
- What should I focus on when starting to implement the feature?
Thanks a million and greetings from Cologne :-)
Maps
- Show cluster of items on a map. Zoom in to see smaller clusters and exact position of items.
- Set radius on a map (wherein something should be found e. g.)
- Set point on map as reference (fixed needle, pan/zooming map)
- Search for a location on map (postal code, street name, POI, etc.)
- use google maps on android and Apple Maps on iOS
In-app purchasing
- Buy a combination of four items (16 combinations)
Notification
- Push notification for three different triggers
Location tracking
- Constantly check where the user is (after agreeing to do so of course)
- Check location against GPS coordinates in server database table
Chat
- Very simple chat for two users to communicate (text only)
Language support
- Change language depending of the language set on the device
- Change language manually
Server communication
- Get items which include an image, plain text and GPS coordinates
- Search through that table on demand and when using location tracking
- Pre-caching of data to minimize server requests (costs)
Android and iOS support
- For everything listed above
- Notch support for both devices e. g.