The fees to topen/close channels were higher than I expected, and they were also not transparent.
I set a low fee (like 3 sat byte) but later on when closing the channel I was charged high fees, and I don't know where they came from. I couldn't set them also.

It's Eclair's fault. I am not sure about c-lightning, but LND allows users to set the closing transaction fee through --sat_per_byte parameter. Even if the implementation supports a certain feature, clients also have to implement it. What was the recommended transaction fee at the time? @LoyceV pointed out that Eclair Mobile overcharges for the closing transaction depending on the mempool state.

LIGHTNING-CLOSE(7)                                                                                                              LIGHTNING-CLOSE(7)

NAME
       lightning-close - Command for closing channels with direct peers

SYNOPSIS
       close id [force] [timeout]

DESCRIPTION
       The close RPC command attempts to close the channel cooperatively with the peer. If the given id is a peer ID (66 hex digits as a string),
       then it applies to the active channel of the direct peer corresponding to the given peer ID. If the given id is a channel ID (64 hex digits
       as a string, or the short channel ID blockheight:txindex:outindex form), then it applies to that channel.

       The close command will time out and return with an error when the number of seconds specified in timeout is reached. If unspecified, it
       times out in 30 seconds.

       The force argument, if the JSON value true, will cause the channel to be unilaterally closed when the timeout is reached. If so, timeout
       will not cause an error, but instead cause the channel to be failed and put onchain unilaterally. Unilateral closes will lead to your funds
       getting locked according to the to_self_delay parameter of the peer.

       Normally the peer needs to be live and connected in order to negotiate a mutual close. Forcing a unilateral close can be used if you
       suspect you can no longer contact the peer.

RETURN VALUE
       On success, an object with fields tx and txid containing the closing transaction are returned. It will also have a field type which is
       either the JSON string mutual or the JSON string unilateral. A mutual close means that we could negotiate a close with the peer, while a
       unilateral close means that the force flag was set and we had to close the channel without waiting for the counterparty.

       A unilateral close may still occur with force set to false if the peer did not behave correctly during the close negotiation.

       Unilateral closes will return your funds after a delay. The delay will vary based on the peer to_self_delay setting, not your own setting.

       On failure, if close failed due to timing out with force argument false, the channel will still eventually close once we have contacted the
       peer.

AUTHOR
       ZmnSCPxj <~redacted~> is mainly responsible.

SEE ALSO
RESOURCES
       Main web site: https://github.com/ElementsProject/lightning

                                                                    04/30/2018                                                  LIGHTNING-CLOSE(7)

I guess it's biggest drawbacks are:

• The learning curve (pretty steep)
• The software: most of it is still in alpha or beta phase... This doesn't show a lot of trust from the dev side (at the moment)
• Not enough open channels to relay all payments effectively

I've been running a site that accepts LN for a rather long time now, and so far everything works fine... But then last week i tried to get payed by a person i personally see as technically competent, and so far i haven't been able to get him to the point where he can succesfully make a LN payment.

I believe every wallet, lightning or not, should let you decide which fee to use.i would use 1 sat byte to close the channel, and waiting 5 days would be ok to me.

As long as you use a custodial service like bluwallet (ios), using LN is pretty easy but custodial services has always been easy to use anyway.

It is a bit pain if you want full control of your funds and for that you need to own your own node and this is where the fun (some might call it pain) starts.

This can be a problem. I know for a fact about one gal that custom set the fees on her greenaddress wallet and waited like a week to see her transaction get the first confirmation. Something like that can happen on the LN too.

I think there should be a noob friend, fire and forget kinda solution for LN.