Remove entry_points support from Gaia and Gecko

NEW
Unassigned

Status

Firefox OS
General
3 years ago
2 years ago

People

(Reporter: kgrandon, Unassigned)

Tracking

(Blocks: 1 bug)

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

3 years ago
Only a single app is still using this. Once it's ported we can remove support for this.
(Reporter)

Updated

3 years ago
Depends on: 1046090
We need to check if some apps in the marketplace are making use of that too.
There's also "inputs" used by the Keyboard app, unfortunately: bug 930371.
(Reporter)

Comment 3

3 years ago
(In reply to Staś Małolepszy :stas from comment #2)
> There's also "inputs" used by the Keyboard app, unfortunately: bug 930371.

I'm not sure of the history there, but that is something we should probably fix. I'm also not sure if it's as big of a pain point as entry_points, does it add complexity to the mozApps API for example?

Let's keep this bug about entry_points, and we can file a new bug about removing the "inputs" field if needed.
Hello, so I see here you are looking to remove the entry_point from Gaia, But I want to know how to differentiate dialer and contact once this change is made, since at the moment we could differentiate them just with the entry point http://mxr.mozilla.org/gaia/source/apps/communications/manifest.webapp#10
Flags: needinfo?(stas)
Flags: needinfo?(fabrice)
We need to have 2 apps, one for the dialer, and one for contacts. The difficulty here is to understand if the data sharing constraints we had are still valid or not. We need the app owners input on that.
Flags: needinfo?(gsvelto)
Flags: needinfo?(francisco)
Flags: needinfo?(fabrice)
We've discussed this a few days ago and we've already started the work to separate the two. Eventually dialer and contacts will be two separate, distinct applications so we'll be able to launch them separately without having to rely on the entry points. From what we could see there's no hard dependencies anymore between the dialer and the contacts app; the only missing bit is UX to switch between the two in a tab-less design. Bug 1097757 was filed for that and we had UX for it but it was decided to not move forward with that, mostly because other work was prioritized at the time. We might want to pick up from there or have something different but this is up to the PMs to decide.
Flags: needinfo?(gsvelto)
Flags: needinfo?(stas)
Agree with comment #6, we don't have any more dependencies, we need to find the time and the solution for have a separated UX, with no contacts embedded within the dialer.
Flags: needinfo?(francisco)
Do we have someone in UX that is dealing with that split?
Flags: needinfo?(firefoxos-ux-bugzilla)
NI Harly - Harly, is the correct spec for the design found in Bug 1097757? Is this a final design?

Thanks for pinging the UX team!
Flags: needinfo?(firefoxos-ux-bugzilla)
oops forgot NI
Flags: needinfo?(hhsu)

Comment 11

2 years ago
Yes, this was the final design done by Carrie for the Tabless call log. If you guys have any questions related to this, please contact Morpheus Chen as he is the UX owner for dialer/contact now.
Flags: needinfo?(hhsu)

Updated

2 years ago
Blocks: 1204894
You need to log in before you can comment on or make changes to this bug.